Expiring Aggressively Those HTTP Cookies
draft-thomson-http-omnomnom-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Martin Thomson , Chris Peterson | ||
| Last updated | 2016-11-27 (Latest revision 2016-05-26) | ||
| Replaced by | draft-ietf-httpbis-rfc6265bis | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
HTTP Cookies that are sent over connections without confidentiality and integrity protection are vulnerable to theft. Such cookies should be expired aggressively.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)