A JSON Encoding for HTTP Header Field Values
draft-reschke-http-jfv-04
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Author | Julian Reschke | ||
| Last updated | 2016-06-23 | ||
| Replaced by | draft-ietf-httpbis-jfv | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-httpbis-jfv, draft-ietf-httpbis-jfv, draft-ietf-httpbis-jfv, draft-ietf-httpbis-jfv | |
| 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 establishes a convention for use of JSON-encoded field values in HTTP header fields.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)