head requests and chunked transfer encoding

Maxim Dounin mdounin at mdounin.ru
Thu Oct 23 15:48:53 MSD 2008


Hello!

On Thu, Oct 23, 2008 at 01:22:38PM +0200, Daniel Crompton wrote:

[...]
> What about the other way round? I send the following:
> 
> POST / HTTP/1.0
> User-Agent: Wget/1.11.3
> Accept: */*
> Host: localhost
> Connection: Keep-Alive
> Content-Type: application/x-www-form-urlencoded
> Transfer-Encoding: chunked
> Content-Length: 142
> 
> <-- body here -->
> 
> And receive:
> 
> HTTP/1.1 411 Length Required

[...]

> I think that somebody took rfc2616 section 4.4 a little to literally:
> <blockquote><i>3. ... If a message is received with both a 
> Transfer-Encoding header field and a Content-Length header field, the 
> latter MUST be ignored.</i></blockquote>
> 
> Content-Length MUST be ignored, but it doesn't mean it should bail with 
> an error. Or am I missing something?

As of now nginx doesn't support chunked encoding from client.

Maxim Dounin





More information about the nginx mailing list