Cookies: HTTP State Management Mechanism
draft-ietf-httpbis-rfc6265bis-03
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
---|---|---|---|
Authors | Adam Barth , Mike West | ||
Last updated | 2019-10-29 (Latest revision 2019-04-27) | ||
Replaces | draft-ietf-httpbis-cookie-prefixes, draft-thomson-http-omnomnom, draft-ietf-httpbis-cookie-same-site, draft-ietf-httpbis-cookie-alone | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Associated WG milestone |
|
||
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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 6265.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)