[
https://issues.apache.org/jira/browse/TS-3828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14660886#comment-14660886
]
ASF GitHub Bot commented on TS-3828:
------------------------------------
Github user zizhong commented on the pull request:
https://github.com/apache/trafficserver/pull/271#issuecomment-128524834
great points. Actually this patch will send the content length. The content
length modified is only in the Http State structure but not in the real
HDRs. The field TransferEncoding is deleted in the current implementation
which will stay deleted in this patch.
On Friday, August 7, 2015, James Peach <[email protected]> wrote:
> Other HTTP servers do send the Content-Length on HEAD requests; I think
> that we should do the same.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/trafficserver/pull/271#issuecomment-128482080>.
>
> 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)
