RFC 2964: Use of HTTP State Management
In plain English — editorial summary, not part of the RFC
This memo identifies specific uses of Hypertext Transfer Protocol (HTTP) State Management protocol which are either (a) not recommended by the IETF, or (b) believed to be harmful, and discouraged. This memo also details additional privacy considerations which are not covered by the HTTP State Management protocol specification. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC2964
- Published
- October 2000
- Authors
- K. Moore; N. Freed
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- —
- Pages
- 8
- Also known as
- BCP44
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2936HTTP MIME Type Handler DetectionCurrent
September 2000
- RFC 2818HTTP Over TLSObsoleted
May 2000
- RFC 2518HTTP Extensions for Distributed Authoring -- WEBDAVObsoleted
February 1999
- RFC 2109HTTP State Management MechanismObsoleted
February 1997
- RFC 2069An Extension to HTTP : Digest Access AuthenticationObsoleted
January 1997
- RFC 4918HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)Updated
June 2007
- RFC 3205On the use of HTTP as a SubstrateObsoleted
February 2002
- RFC 2376XML Media TypesObsoleted
July 1998
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?