Issue 421785 in chromium: net::ERR_CONNECTION_CLOSED on secure connection attempt

54 views
Skip to first unread message

chro...@googlecode.com

unread,
Oct 9, 2014, 5:00:55 AM10/9/14
to chromi...@chromium.org
Status: Unconfirmed
Owner: ----
Labels: Cr-Internals-Network Pri-2 Via-Wizard Type-Bug OS-Mac

New issue 421785 by JRad...@gmail.com: net::ERR_CONNECTION_CLOSED on secure
connection attempt
https://code.google.com/p/chromium/issues/detail?id=421785

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_0)
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2182.0 Safari/537.36

Example URL:
https://www.pekao24.pl/

Steps to reproduce the problem:
1. go to https://www.pekao24.pl/
2. enter any number
3. press enter

What is the expected behavior?

What went wrong?
POST request to https://www.pekao24.pl/MCP/PINVerification.htm fails with
net::ERR_CONNECTION_CLOSED which results with either defunct password page
or just a blank page.

Did this work before? Yes about 3-4 weeks ago

Chrome version: 40.0.2182.0 Channel: canary
OS Version: OS X 10.10.0
Flash Version: Shockwave Flash 15.0 r0

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

unread,
Oct 9, 2014, 10:30:09 AM10/9/14
to chromi...@chromium.org

Comment #1 on issue 421785 by mme...@chromium.org:
net::ERR_CONNECTION_CLOSED on secure connection attempt
https://code.google.com/p/chromium/issues/detail?id=421785

Can't repro. Could you upload a net-internals dump
(https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details)?

chro...@googlecode.com

unread,
Oct 11, 2014, 9:40:37 AM10/11/14
to chromi...@chromium.org

Comment #4 on issue 421785 by JRad...@gmail.com: net::ERR_CONNECTION_CLOSED
Yep, still happens. Attaching full net-internals log.

Attachments:
net-internals-log.json 150 KB

chro...@googlecode.com

unread,
Oct 11, 2014, 4:54:22 PM10/11/14
to chromi...@chromium.org

Comment #5 on issue 421785 by mme...@chromium.org:
net::ERR_CONNECTION_CLOSED on secure connection attempt
https://code.google.com/p/chromium/issues/detail?id=421785

Thanks for the log! It's nice and clean, with a minimum of random extra
stuff going on.

We send a POST over SSL, with the headers and body merged, since the body
is so small.

Looks like we're getting a Connection: close HTTP/1.1 response without a
Content-Length, so the connection closing should be interpreted as the end
of stream, but for some reason, that's not happening.

chro...@googlecode.com

unread,
Oct 13, 2014, 9:26:33 PM10/13/14
to chromi...@chromium.org

Comment #6 on issue 421785 by glo...@gmail.com: net::ERR_CONNECTION_CLOSED
I can reproduce on 40.0.2185.0 canary (64-bit), and 40.0.2188.1 canary
(64-bit). Is there a flag that I can toggle to change the behavior? I can't
figure out why else it would work for pucchaka...@chromium.org, but not
some.

chro...@googlecode.com

unread,
Oct 14, 2014, 9:15:03 PM10/14/14
to chromi...@chromium.org

Comment #7 on issue 421785 by priyajeet: net::ERR_CONNECTION_CLOSED on
Also see Issue 422246

chro...@googlecode.com

unread,
Oct 16, 2014, 3:28:58 PM10/16/14
to chromi...@chromium.org

Comment #8 on issue 421785 by mbo...@chromium.org:
net::ERR_CONNECTION_CLOSED on secure connection attempt
https://code.google.com/p/chromium/issues/detail?id=421785

Tested on latest Chrome 40.0.2188.2 dev - Mac 10.9.5 with steps to
reproduce and same behavior observed as in #3.

JRadosz@: Try the following:
1. This issue might be due to extensions installed. Please disable
third-party extensions(except default), relaunch Chrome and see if the
issue is still reproducible.
2. Please check in new profile by going to Chrome://settings -> Add new
user.

chro...@googlecode.com

unread,
Feb 4, 2015, 12:48:48 PM2/4/15
to chromi...@chromium.org

Comment #13 on issue 421785 by lifewate...@gmail.com:
net::ERR_CONNECTION_CLOSED on secure connection attempt
https://code.google.com/p/chromium/issues/detail?id=421785

I am seeing this too. I think it has to do with latency. I am on
satellite and it usually works after the 2nd or 3rd retry.
Reply all
Reply to author
Forward
0 new messages