Re: Issue 373811 in chromium: chrome fires random net::ERR_CONNECTION_CLOSED error when posting a payload

[chro...@googlecode.com]

Comment #6 on issue 373811 by swan...@gmail.com: chrome fires random
net::ERR_CONNECTION_CLOSED error when posting a payload
http://code.google.com/p/chromium/issues/detail?id=373811

i tried to get some wireshark trace. couldn't decrypt the content. but at
the end, I see that there is a Fin signal first coming from server, and
then a Fin signal send back by client.


--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Comment #7 on issue 373811 by swan...@gmail.com: chrome fires random

net::ERR_CONNECTION_CLOSED error when posting a payload
http://code.google.com/p/chromium/issues/detail?id=373811

screen of the last couple network events when the issue happens.

Attachments:
Screen Shot 2014-05-15 at 10.54.06 PM.png 62.8 KB

[chro...@googlecode.com]

Updates:
Labels: Needs-Feedback

Comment #8 on issue 373811 by manoranj...@chromium.org: chrome fires random

net::ERR_CONNECTION_CLOSED error when posting a payload
http://code.google.com/p/chromium/issues/detail?id=373811

cbentzel@, Could you please look into this?

Thank you.

[chro...@googlecode.com]

Updates:
Status: Assigned
Owner: jgraetti...@chromium.org
Labels: Cr-Internals-Network-SPDY

Comment #9 on issue 373811 by cben...@chromium.org: chrome fires random

net::ERR_CONNECTION_CLOSED error when posting a payload
http://code.google.com/p/chromium/issues/detail?id=373811

jgraettinger: See event 39960 in the net-internals log from comment #3

This is all over SPDY to a twitter server.

In that case we do a very large post, get a 200 response from the server,
but then there is a SPDY_STREAM_ERROR when reading the response body.

t=37889 [st=13846] +HTTP_TRANSACTION_READ_BODY [dt=1]
t=37890 [st=13847] SPDY_STREAM_UPDATE_RECV_WINDOW
--> delta = -218
--> stream_id = 3
--> window_size = 10485542
t=37890 [st=13847] SPDY_STREAM_ERROR
--> description = "ABANDONED (stream_id=3):
https://ton-stg.smf1.twitter.com/i/upload.iframe"
--> status = -100
--> stream_id = 3
t=37890 [st=13847] -HTTP_TRANSACTION_READ_BODY
--> net_error = -100 (ERR_CONNECTION_CLOSED)
t=37890 [st=13847] FAILED
--> net_error = -100 (ERR_CONNECTION_CLOSED)
t=37890 [st=13847] -REQUEST_ALIVE
--> net_error = -100 (ERR_CONNECTION_CLOSED)

It's possible this is a SPDY server bug on Twitter's end, although I would
expect the same behavior in FF if that is the case (not Safari since it
doesn't speak SPDY).

[chro...@googlecode.com]

Comment #10 on issue 373811 by cben...@chromium.org: chrome fires random

net::ERR_CONNECTION_CLOSED error when posting a payload
http://code.google.com/p/chromium/issues/detail?id=373811

Also note that this runs into lots of flow control stalls when uploading
which may make it feel slow to upload, but that shouldn't impact the
ERR_CONNECTION_CLOSED response.

[chro...@googlecode.com]

Comment #12 on issue 373811 by swan...@gmail.com: chrome fires random

net::ERR_CONNECTION_CLOSED error when posting a payload
http://code.google.com/p/chromium/issues/detail?id=373811

Agree this is probably a server side issue. Will look into it on our end.

Thanks.

[chro...@googlecode.com]

Updates:
Status: WontFix

Comment #13 on issue 373811 by jgraetti...@chromium.org: chrome fires

random net::ERR_CONNECTION_CLOSED error when posting a payload
http://code.google.com/p/chromium/issues/detail?id=373811

Sounds good, please re-open this issue if needed. Cheers,