[
https://issues.apache.org/jira/browse/TS-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yunkai Zhang updated TS-1062:
-----------------------------
Description:
1) Introduce extended FetchSM APIs, which will be used by SPDY.
2) Make TSFetchUrl() dechunk encoding automatically:
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).
was:
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).
> Introduce extended FetchSM API
> ------------------------------
>
> 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: Yunkai Zhang
> Fix For: sometime
>
> Attachments: 0001-TS-1062-Extends-and-optimizes-FetchSM.patch,
> 0002-TS-1062-Implement-dechunk-supporting-for-extended-Fe.patch,
> 0003-TS-1062-Make-TSFetchUrl-handle-chunked-encoding-auto.patch
>
>
> 1) Introduce extended FetchSM APIs, which will be used by SPDY.
> 2) Make TSFetchUrl() dechunk encoding automatically:
> 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.2#6252)
