zrhoffman commented on issue #3965: Traffic Router inconsistent behavior on HTTP HEAD requests URL: https://github.com/apache/trafficcontrol/issues/3965#issuecomment-546920662 The wait itself is wontfix cURL-specific behavior. From [a curl-users mailing list thread](https://curl.haxx.se/mail/archive-2015-11/0021.html): > The difference in the HTTP protocol between a HEAD and a GET response is that a HEAD response is _exactly_ the same as the GET response except that there's no response body. Since curl knows it sent a GET request, it will wait for a response body if the response headers indicate there is one. If curl knows it sent a HEAD it will just not wait for a response, even if the headers say there is one, since it knows a server will never send a response body to such a request. That said, setting a content length does get rid of the timeout. As a proof-of-concept, I have added the `Content-Length` header for steering responses on a branch: https://github.com/apache/trafficcontrol/compare/a5a4bb9012...zrhoffman:set_content_length Would we also want to ensure a content length for the TR API?
---------------------------------------------------------------- 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: [email protected] With regards, Apache Git Services
