Hypertext Transport Protocol (HTTP) Session Continuation: Problem Statement
draft-ietf-websec-session-continue-prob-00
| Document | Type |
Expired Internet-Draft
(websec WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Nicolás Williams | ||
| Last updated | 2014-01-08 (Latest revision 2013-07-07) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| 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
One of the most often talked about problems in web security is "cookies". Web cookies are a method of associating requests with "sessions" that may have been authenticated somehow. Cookies are a form of bearer token that leave much to be desired. This document describes the session "continuation" problem for the HyperText Transport Protocol (HTTP).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)