Advisory Content-Length for HTTP
draft-nottingham-bikeshed-length-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Mark Nottingham | ||
| Last updated | 2020-09-18 (Latest revision 2020-03-17) | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| 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 can be found at:
https://www.ietf.org/archive/id/draft-nottingham-bikeshed-length-00.txt
https://www.ietf.org/archive/id/draft-nottingham-bikeshed-length-00.txt
Abstract
The HTTP Content-Length header field is overloaded with (at least) two duties: message delimitation in HTTP/1, and metadata about the length of an incoming request body to the software handling it. This causes confusion, and sometimes problems. This document proposes a new header to untangle these semantics (at least partially).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)