You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by GitBox <gi...@apache.org> on 2019/11/08 15:43:46 UTC

[GitHub] [trafficcontrol] rob05c edited a comment on issue #3965: Traffic Router inconsistent behavior on HTTP HEAD requests

rob05c edited a comment on issue #3965: Traffic Router inconsistent behavior on HTTP HEAD requests
URL: https://github.com/apache/trafficcontrol/issues/3965#issuecomment-551876550
 
 
   I don't object to the change itself, but I have concerns about what's driving it.
   
   The HTTP Spec says servers MUST NOT send `Content-Length` if they use Chunked encoding, and clients MUST accept Chunked encoding.
   
   Therefore, any Clients which require `Content-Length` are in violation of HTTP.
   
   >actually, Content-Length is one of the payload headers that MAY be omitted in a HEAD response.
   
   Right. So, the server isn't in violation of the spec here, it's permitted to include Tranfer-Encoding. But I agree, it probably shouldn't.
   
   But moreover, Transfer-Encoding is a payload field, and HEAD payloads have no defined semantics. So, if it's confusing any clients, those clients are violating the HTTP spec.
   
   So again, it doesn't seem wrong to change the server (maybe even following the Robustness Principle). But we should fix the broken clients driving this.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services