According to RFC 2616 the HEAD response MUST NOT
return a message-body in the response:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.4
Right. I *think* the problem that Sylvain is bringing to light is that a different headers are being returned for HEAD and GET requests. From the section of RFC 2616 that you referenced above:
"The metainformation contained in the HTTP headers in response to a HEAD request SHOULD be identical to the information sent in response to a GET request."
So if an app/middleware sets what it deems to be the correct Content-Length for a resource in response to a HEAD request, it gets overridden by the server, which sets it to zero.
Christian
http://www.dowski.com
_______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
