[ https://issues.apache.org/jira/browse/TS-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13995943#comment-13995943 ]
Bryan Call edited comment on TS-2791 at 5/13/14 2:01 AM: --------------------------------------------------------- [~sudheerv] Did you try to set TS_FETCH_FLAGS_STREAM? I would like to know more details about why header_done is not being set. {code} if (header_done == 0 && ((fetch_flags & TS_FETCH_FLAGS_STREAM) || callback_options == AFTER_HEADER)) { if (client_response_hdr.parse_resp(&http_parser, resp_reader, &bytes_used, 0) == PARSE_DONE) { header_done = 1; {code} was (Author: bcall): [~sudheerv] Did you try set TS_FETCH_FLAGS_STREAM? I would like to know more details about why header_done is not being set. {code} if (header_done == 0 && ((fetch_flags & TS_FETCH_FLAGS_STREAM) || callback_options == AFTER_HEADER)) { if (client_response_hdr.parse_resp(&http_parser, resp_reader, &bytes_used, 0) == PARSE_DONE) { header_done = 1; {code} > 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)