Use of HTTP State Management

Metadata

Publisher: IETF
Doc Type: Best Practice
Pages: 8
Abstract: 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.
Publication Date: 2000-10-01
Status Note: Best Current Practice
DOI: 10.17487/RFC2964
Link: https://doi.org/10.17487/RFC2964
Author(s): Keith Moore
Ned Freed
Keyword(s): HTTP

Latest version of IETF RFC 2964

Document Versions — IETF RFC 2964

▶ IETF RFC 2964 (2000-10-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Bibliographic Reference(s)

IETF RFC 1123 [Active*]
IETF RFC 2109 [Superseded*]
IETF RFC 2965 [Superseded*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC2964.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 2964, Use of HTTP State Management. Available at https://doi.org/10.17487/RFC2964

Snippet:

IETF RFC 2964, Use of HTTP State Management. Available at https://doi.org/10.17487/RFC2964

HTML (ISO 690 compliant)

Preview:

IETF RFC 2964, Use of HTTP State Management. Available at https://doi.org/10.17487/RFC2964

Snippet:

<span class="citation"><cite>IETF RFC 2964</cite>, Use of HTTP State Management. Available at <a href="https://doi.org/10.17487/RFC2964" target="_blank" rel="noopener">https://doi.org/10.17487/RFC2964</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 2964, Use of HTTP State Management
doi: 10.17487/RFC2964
url: https://doi.org/10.17487/RFC2964

Snippet:

<li>
<cite id="bib-rfc2964">IETF RFC 2964</cite>, Use of HTTP State Management
<span class="doi">10.17487/RFC2964</span>
</li>

Referenced By

IETF RFC 8216 [Active*]