[
https://issues.apache.org/jira/browse/TS-3828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14659710#comment-14659710
]
ASF GitHub Bot commented on TS-3828:
------------------------------------
GitHub user zizhong opened a pull request:
https://github.com/apache/trafficserver/pull/271
TS-3828: HEAD requests hang when origin returns Transfer-Encoding: Chunked
When a client makes a HEAD request and the origin returns a header
containing Transfer-Encoding: chunked or Content-Length, ATS now waits for the
http body which will never come. Then the ATS goes though several timeouts
whose length is configured by the record called
proxy.config.http.transaction_no_activity_timeout_out.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zizhong/trafficserver TS-3828
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/271.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #271
----
commit aa9b94fab4020798b81a749f6e5994387f7a09c9
Author: Zizhong Zhang <[email protected]>
Date: 2015-08-06T08:49:50Z
TS-3828: HEAD requests hang when origin returns Transfer-Encoding: Chunked
commit d7fa8ccdde14b205ebb6ce423df7313e69574794
Author: Zizhong Zhang <[email protected]>
Date: 2015-08-06T08:51:54Z
TS-3828: HEAD requests hang when origin returns Transfer-Encoding: Chunked.
ADD TESTS
----
> 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
>
> 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)
