[
https://issues.apache.org/jira/browse/TS-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13995975#comment-13995975
]
Sudheer Vinukonda edited comment on TS-2791 at 5/13/14 2:48 AM:
----------------------------------------------------------------
Hi Bryan -
A new FetchSM is created for every SYN_STREAM handling within a SPDY
connection. TS_FETCH_FLAGS_STREAM is set during FetchSM initialization
(FetchSM::ext_init) - I've confirmed this with debug logs as well.
>From what I can see, the flag header_done appears to be needed when sending
>response to a client (based on the way it is set by checking
>client_response_hdr.parse_resp()) . For sending a client request to the origin
>(that involves POST/PUT), header_done is probably not applicable.
was (Author: sudheerv):
Hi Bryan -
TS_FETCH_FLAGS_STREAM is already set during FetchSM initialization
(FetchSM::ext_init) - I've confirmed this with debug logs as well.
>From what I can see, the flag header_done appears to be needed when sending
>response to a client (based on the way it is set by checking
>client_response_hdr.parse_resp()) . For sending a client request to the origin
>(that involves POST/PUT), header_done is probably not applicable.
> SPDY POST transactions failing with ERR_CLIENT_ABORT
> ----------------------------------------------------
>
> Key: TS-2791
> URL: https://issues.apache.org/jira/browse/TS-2791
> Project: Traffic Server
> Issue Type: Bug
> Components: SPDY
> Reporter: Sudheer Vinukonda
> Labels: spdy, yahoo
> Fix For: sometime
>
> Attachments: ts2791.diff
>
>
> During our production testing of SPDY, we noticed that when trying to compose
> mails (POST transactions) on Firefox, we are seeing "Network Error" from the
> browser and ERR_CLIENT_ABORT from squid.logs. Upon some analysis, this issue
> appears to be likely specific to SPDY transactions and seem to be triggered
> by the expiry of proxy.config.http.transaction_no_activity_timeout_in timer.
> After some investigation, it looks like this may be caused by a timing issue
> related to streaming of the POST data to the origin.. If the POST body (data)
> is available by the time client session and origin connection is ready, the
> POST is successful, but, if the data is large enough that it is not all read
> yet by the time origin connection is established, the streaming does not get
> triggered. Debugging further to identify the root cause.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
