[
https://issues.apache.org/jira/browse/TS-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13918115#comment-13918115
]
Yunkai Zhang edited comment on TS-1062 at 3/3/14 2:56 PM:
----------------------------------------------------------
Hi guys:
I have split extended FetchSM's patch from SPDY ticket(TS-2431) to here.
Both
[0001-TS-1062-Extends-and-optimizes-FetchSM.patch|https://issues.apache.org/jira/secure/attachment/12632267/0001-TS-1062-Extends-and-optimizes-FetchSM.patch]
and
[0002-TS-1062-Implement-dechunk-supporting-for-extended-Fe.patch|https://issues.apache.org/jira/secure/attachment/12632268/0002-TS-1062-Implement-dechunk-supporting-for-extended-Fe.patch]
are well tested, they should be stable.
But
[0003-TS-1062-Make-TSFetchUrl-handle-chunked-encoding-auto.patch|https://issues.apache.org/jira/secure/attachment/12632269/0003-TS-1062-Make-TSFetchUrl-handle-chunked-encoding-auto.patch]
hasn't been tested, since I do not have plugin that depends on TSFetchUrl()
API.
Can any one help me to test TSFetchUrl() API with these patches?
I need your feedbacks:).
was (Author: yunkai):
Hi guys:
I have split extended FetchSM's patch from SPDY ticket(TS-2431) to here.
Both
[0001-TS-1062-Extends-and-optimizes-FetchSM.patch|https://issues.apache.org/jira/secure/attachment/12632263/0001-TS-1062-Extends-and-optimizes-FetchSM.patch]
and
[0002-TS-1062-Implement-dechunk-supporting-in-FetchSM.patch|https://issues.apache.org/jira/secure/attachment/12632264/0002-TS-1062-Implement-dechunk-supporting-in-FetchSM.patch]
are well tested, they should be stable.
But
[0003-TS-1062-Make-TSFetchUrl-handle-chunked-encoding-auto.patch|https://issues.apache.org/jira/secure/attachment/12632265/0003-TS-1062-Make-TSFetchUrl-handle-chunked-encoding-auto.patch]
hasn't been tested, since I do not have plugin that depends on TSFetchUrl()
API.
Can any one help me to test TSFetchUrl() API with these patches?
I need your feedbacks:).
> 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: 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
>
>
> 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)
