[
https://issues.apache.org/jira/browse/TS-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876413#comment-13876413
]
Yunkai Zhang commented on TS-1062:
----------------------------------
I have extended FetchSM in SPDY series patches, and FetchSM has supported
chunked encoding:
https://issues.apache.org/jira/secure/attachment/12623483/0004-TS-2431-Implement-dechunk-supporting-in-FetchSM.V2.patch
> 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: sometime
>
>
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)
