[
https://issues.apache.org/jira/browse/TS-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877402#comment-13877402
]
Yunkai Zhang commented on TS-1062:
----------------------------------
When I extended FetchSM, one of principle is that to keep backward
compatibility, so that other old plugins can still work with new code.
It's easy to land or refine my FetchSM's patches, they are totally independent
from other SPDY code. I think the SPDY code is the best example about how to
use the extended API of FetchSM.
I hope you can review it as much as quickly.
> 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)
