[GitHub] [trafficcontrol] guzzijason commented on issue #3965: Traffic Router inconsistent behavior on HTTP HEAD requests
guzzijason commented on issue #3965: Traffic Router inconsistent behavior on HTTP HEAD requests URL: https://github.com/apache/trafficcontrol/issues/3965#issuecomment-552014356 Nope. See my examples of the current GET/HEAD responses in the issue description. 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: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [trafficcontrol] guzzijason commented on issue #3965: Traffic Router inconsistent behavior on HTTP HEAD requests
guzzijason commented on issue #3965: Traffic Router inconsistent behavior on HTTP HEAD requests URL: https://github.com/apache/trafficcontrol/issues/3965#issuecomment-551955244 But why do we bother to send `Transfer-Encoding: chunked` on a HEAD response with no body? Even if the spec says we can, should we be? Seems to serve no purpose. 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: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [trafficcontrol] guzzijason commented on issue #3965: Traffic Router inconsistent behavior on HTTP HEAD requests
guzzijason commented on issue #3965: Traffic Router inconsistent behavior on HTTP HEAD requests URL: https://github.com/apache/trafficcontrol/issues/3965#issuecomment-547049866 Sorry... actually, `Content-Length` is one of the payload headers that MAY be omitted in a HEAD response. At any rate, keeping that header as part of the HEAD response is still RFC-compliant behavior. I think the bigger problem is the `Transfer-Encoding: chunked` header, which is NOT part of the standard HTTP GET request from TR. Its unclear why we would want TR to send that at in any case of a 302 response. 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: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [trafficcontrol] guzzijason commented on issue #3965: Traffic Router inconsistent behavior on HTTP HEAD requests
guzzijason commented on issue #3965: Traffic Router inconsistent behavior on HTTP HEAD requests URL: https://github.com/apache/trafficcontrol/issues/3965#issuecomment-547047350 Per RFC 7231: ``` The server SHOULD send the same header fields in response to a HEAD request as it would have sent if the request had been a GET, except that the payload header fields (Section 3.3) MAY be omitted. ``` TR sends `Content-Length: 0` as part of a HTTP GET response, so based on the RFC recommended behavior, then I believe it should do the same in response to an HTTP HEAD. 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: us...@infra.apache.org With regards, Apache Git Services
