W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2012

Re: P1: Content-Length SHOULD be sent

From: Willy Tarreau <w@1wt.eu>
Date: Tue, 27 Nov 2012 07:05:16 +0100
To: Mark Nottingham <mnot@mnot.net>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <20121127060516.GK28405@1wt.eu>
On Tue, Nov 27, 2012 at 04:21:25PM +1100, Mark Nottingham wrote:
> Currently, p1 says:
> 
> > When a message is allowed to contain a message body, does not have a Transfer-Encoding header field, and has a payload body length that is known to the sender before the message header section has been sent, the sender should send a Content-Length header field to indicate the length of the payload body as a decimal number of octets.
> 
> This unqualified SHOULD leads people to convoluted readings of the spec where Content-Length is required to be sent on a GET request:
>   https://github.com/kennethreitz/requests/issues/223#issuecomment-10745532
> 
> Proposal:
> 
> > When a message is allowed to contain a body, does not have a Transfer-Encoding header field, and has a payload body length that is known to the sender before the message header section has been sent, the sender should send a Content-Length header field to indicate the length of the payload body as a decimal number of octets, unless the message is a request and the payload length is zero (in which case the Content-Length header MAY be sent). 

Seems fine to me too.

Willy
Received on Tuesday, 27 November 2012 06:05:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 November 2012 06:05:45 GMT