[ https://issues.apache.org/jira/browse/TS-3828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14660580#comment-14660580 ]
William Bardwell commented on TS-3828: -------------------------------------- Just to be clear, be careful that you do not delete/zero out the Content-Length header in the client response to a HEAD request. That would break lots of things. > HEAD requests hang when origin returns Transfer-Encoding: Chunked > ----------------------------------------------------------------- > > Key: TS-3828 > URL: https://issues.apache.org/jira/browse/TS-3828 > Project: Traffic Server > Issue Type: Bug > Components: Core > Reporter: Brian Geffon > Assignee: Brian Geffon > Fix For: 6.0.0 > > > When a client makes a HEAD request and the origin returns a header containing > Transfer-Encoding: chunked ATS for some reason adds a ChunkedConsumer to > dechunk the body (which will never arrive) in some cases ATS will not return > the headers to the client resulting in a 502, or in other cases it will send > the headers and then close the connection later thinking the origin timed > out. In both cases the behavior is incorrect. -- This message was sent by Atlassian JIRA (v6.3.4#6332)