Non-HTTP Cookies
draft-west-nonhttp-cookies-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mike West | ||
| Last updated | 2017-12-08 (Latest revision 2017-06-06) | ||
| RFC stream | (None) | ||
| Intended RFC status | (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
This document updates RFC6265 by defining a "NonHttp" attribute which ensures that a given cookie is available only to "non-HTTP" APIs. Yes, it is a little strange for "HTTP State Management" to support exclusively non-HTTP use cases, but the internet is a strange place. So it goes.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)