HTTP State Management Mechanism
Metadata
- Publisher
- IETF
- Doc Type
- Specification
- Pages
- 21
- Abstract
- This document specifies a way to create a stateful session with HTTP requests and responses. It describes two new headers, Cookie and Set- Cookie, which carry state information between participating origin servers and user agents. The method described here differs from Netscape's Cookie proposal, but it can interoperate with HTTP/1.0 user agents that use Netscape's method. [STANDARDS-TRACK]
- Publication Date
- 1997-02-01
- Status Note
- Historic
- DOI
10.17487/RFC2109- Link
- https://doi.org/10.17487/RFC2109
- Author(s)
- David M. KristolLou Montulli
- Keyword(s)
- HTTP-STATE, HTTP, Cookie
Latest version of IETF RFC 2109
Document Versions — IETF RFC 2109
-
▶ IETF RFC 2109 (1997-02-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC2109.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 2109, HTTP State Management Mechanism. Available at https://doi.org/10.17487/RFC2109
Snippet:
IETF RFC 2109, HTTP State Management Mechanism. Available at https://doi.org/10.17487/RFC2109
HTML (ISO 690 compliant)
Preview:
IETF RFC 2109, HTTP State Management Mechanism. Available at https://doi.org/10.17487/RFC2109
Snippet:
<span class="citation"><cite>IETF RFC 2109</cite>, HTTP State Management Mechanism. Available at <a href="https://doi.org/10.17487/RFC2109" target="_blank" rel="noopener">https://doi.org/10.17487/RFC2109</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 2109, HTTP State Management Mechanism
doi: 10.17487/RFC2109
url: https://doi.org/10.17487/RFC2109
doi: 10.17487/RFC2109
url: https://doi.org/10.17487/RFC2109
Snippet:
<li> <cite id="bib-rfc2109">IETF RFC 2109</cite>, HTTP State Management Mechanism <span class="doi">10.17487/RFC2109</span> </li>
Referenced By
- IETF RFC 2458 [Active*]
- IETF RFC 2965 [Superseded*]
- IETF RFC 6265 [Active*]