RFC 2109: HTTP State Management Mechanism
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2965.
Current document in this lineage: RFC 6265 — HTTP State Management Mechanism
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC2109
- Published
- February 1997
- Authors
- D. Kristol; L. Montulli
- Status
- HISTORIC
- Stream
- IETF
- Area
- app
- Pages
- 21
- Also known as
- —
- Obsoleted by:
- RFC 2965
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2109 (1997)
- RFC 2965 (2000)
- RFC 6265 (2011) ✓
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2069An Extension to HTTP : Digest Access AuthenticationObsoleted
January 1997
- RFC 2518HTTP Extensions for Distributed Authoring -- WEBDAVObsoleted
February 1999
- RFC 2936HTTP MIME Type Handler DetectionCurrent
September 2000
- RFC 4918HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)Updated
June 2007
- RFC 2818HTTP Over TLSObsoleted
May 2000
- RFC 2964Use of HTTP State ManagementCurrent
October 2000
- RFC 2156MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIMECurrent
January 1998
- RFC 2186Internet Cache Protocol (ICP), version 2Current
September 1997
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?