CGI is, of course, good and all, but sometimes it's nice to know what's going on "under the hood." This can be useful to know if you're in the testing phase and want to be sure your cookie's being read or sent.

When a page sets a cookie on a browser, all it's doing (usually) is adding this line to its headers:

Set-Cookie: name=value; expires=(date)

plus any path you specify. When a cookie-enabled browser requests another page from the domain (or path in that domain specified by the cookie), it adds its own Cookie: header to its request. This is available as $ENV{HTTP_COOKIE}.

BCE
--Your punctuation skills are insufficient!