[
https://issues.apache.org/jira/browse/TS-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Peach updated TS-1062:
----------------------------
Fix Version/s: (was: 3.1.4)
3.2.0
Not a regression; push out to 3.2.
> TSFetchUrl doesn't handle chunked encoding
> ------------------------------------------
>
> Key: TS-1062
> URL: https://issues.apache.org/jira/browse/TS-1062
> Project: Traffic Server
> Issue Type: Bug
> Components: TS API
> Reporter: James Peach
> Assignee: James Peach
> Fix For: 3.2.0
>
>
> If you use TSFetchUrl() to fetch a resource and the response comes back with
> chunked encoding, you are basically hosed. The caller never gets the SUCCESS
> event because FetchSM does not know how to decode the body. There's no
> content-length header and the origin server doesn't drop the TCP connection,
> so we just sit there waiting for the response to finish forever (well until
> the origin server drops the connection 10s later).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
