RFC 6265: HTTP State Management Mechanism
In plain English — editorial summary, not part of the RFC
This document defines the HTTP Cookie and Set-Cookie header fields. These header fields can be used by HTTP servers to store state (called cookies) at HTTP user agents, letting the servers maintain a stateful session over the mostly stateless HTTP protocol. Although cookies have many historical infelicities that degrade their security and privacy, the Cookie and Set-Cookie header fields are widely used on the Internet. This document obsoletes RFC 2965. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6265
- Published
- April 2011
- Authors
- A. Barth
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 37
- Also known as
- —
- Obsoletes:
- 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)
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2109HTTP State Management MechanismObsoleted
February 1997
- RFC 6518Keying and Authentication for Routing Protocols (KARP) Design GuidelinesCurrent
February 2012
- RFC 5751Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message SpecificationObsoleted
January 2010
- RFC 5750Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Certificate HandlingObsoleted
January 2010
- RFC 4765The Intrusion Detection Message Exchange Format (IDMEF)Current
March 2007
- RFC 8471The Token Binding Protocol Version 1.0Current
October 2018
- RFC 8472Transport Layer Security (TLS) Extension for Token Binding Protocol NegotiationCurrent
October 2018
- RFC 8473Token Binding over HTTPCurrent
October 2018
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?