| |
| |
RFC2109 (Site not responding. Last check: 2007-10-09) |
 | | RFC 2109 HTTP State Management Mechanism February 1997 The VALUE is opaque to the user agent and may be anything the origin server chooses to send, possibly in a server-selected printable ASCII encoding. |
 | | RFC 2109 HTTP State Management Mechanism February 1997 * Cache the received response subject to the control of the usual headers, such as Expires, Cache-control: no-cache, and Cache- control: private, * Cache the Set-Cookie subject to the control of the usual header, Cache-control: no-cache="set-cookie". |
 | | RFC 2109 HTTP State Management Mechanism February 1997 While both session IDs and cookies can provide a way to sustain stateful sessions, their intended purpose is different, and, consequently, the privacy requirements for them are different. |
| rfc.net /rfc2109.html (5430 words) |
|