Webmaster in a Nutshell, Second Edition

Cookies

Persistent-state, client-side cookies were introduced by Netscape Navigator to enable a server to store client-specific information on the client’s machine and use that information when a server or a particular page is accessed again by the client. The cookie mechanism allows servers to personalize pages for each client, or remember selections the client has made when browsing through various pages of a site—all without having to use a complicated (or more time-consuming) CGI/database system on the server’s side.

Cookies work in the following way: when a CGI program identifies a new user, it adds an extra header to its response containing an identifier for that user and other information the server may glean from the client’s input. This header informs the cookie-enabled browser to add this information to the client’s cookies file. After this, all requests to that URL from the browser will include the cookie information as an extra header in the request. The CGI program uses this information to return a document tailored to that specific client. The cookies are stored on the client user’s hard drive, so the information remains even when the browser is closed and reopened.

The Set-Cookie Response Header

A cookie is created when a client visits a site or page for the first time. A CGI program looks for previous cookie information in the client request and, if it is not there, sends a response containing a Set-Cookie header. This header contains a name/value pair (the actual ...