What type of HTTP session tracking artifact is designed to expire once a user's web browser session is closed?

URL Session IDs embed the session token in the query string of every URL, which persists in browser history, server logs, and HTTP referrer headers long after the browser closes.

Client-side certificates are X.509 certificates stored in the operating system certificate store for mutual TLS authentication and are not HTTP session-tracking artifacts.

Hidden form fields store values within HTML form POST submissions and exist only for a single page interaction; they provide no session continuity across requests and have no browser-session expiry mechanism.

Non-persistent cookies, also known as session cookies, are held in volatile browser memory with no explicit expiration date, so the browser discards them the moment the session ends. This behavior is intentional for transient artifacts like authentication tokens that must not survive a closed browser. Unlike persistent cookies written to disk with a future expiry timestamp, session cookies leave no residual data after the browser closes.