[jira] [Comment Edited] (TS-2791) SPDY POST transactions failing with ERR_CLIENT_ABORT

["Sudheer Vinukonda (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994130#comment-13994130 ] 

Sudheer Vinukonda edited comment on TS-2791 at 5/10/14 10:46 AM:
-----------------------------------------------------------------

So, the above fix seems to work - POST requests are now successful with this fix. 

I am yet to verify that the fix will still work if I limit it to method PURGE. 

But, in the mean time, can Yunkai Zhang comment on whether this fix might cause any other side affects?


was (Author: sudheerv):
So, the above fix seem to help - POST requests are now successful with this fix. 

I am yet to verify that the fix will still work if I check for the method to PURGE alone. 

But, in the mean time, can Yunkai Zhang comment on whether this fix might cause any other side affects?

> 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
>
> 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)