Protocols
Saved & recent

Session

Also called: web session, login session, session identifier

A web session connects separate requests to a continuing application context, such as a signed-in account. In a common design, the browser holds an unpredictable session identifier in a cookie while the server stores the associated state. The cookie is the delivery mechanism; the session also includes the server’s rules for creation, expiry and invalidation.

For example, a museum site maps a session identifier to a visitor’s account and pending bookings. After login it replaces the identifier to reduce session-fixation risk. Logout invalidates the server-side session as well as clearing the browser cookie. Merely deleting a cookie does not prevent a copied identifier from being accepted by an unchanged server.

Read first
HTTP cookies
Related
HTTP cookies, Authentication, Cross-site request forgery
Further reading
OWASP — Session Management Cheat Sheet
browser server HTTP request carries session ID opaque cookie ID ID account pending bookings server session record logout cookie cleared server row invalidated old identifier rejected afterward
The cookie carries fictitious identifier S7; the server holds the account and booking state. Logout clears the cookie and invalidates the server-side association, so a copied old S7 is rejected.

View in the full Protocols collection