Intermittent issue: HTTP Request fails; error in event log: net_error = -100 (ERR_CONNECTION_CLOSED)
Reported by
honey.se...@gmail.com,
Mar 27 2018
|
||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.162 Safari/537.36 Steps to reproduce the problem: 1. Open our application 2. Intermittently service request got failed 3. What is the expected behavior? What went wrong? Intermittently our service requests get failed. In the attached event logs, one of our serviceRequest to applicationservice.com intermittenly fails gets net_error":-100 (connection_closed) line no. 161-162. Did this work before? No Does this work in other browsers? Yes Chrome version: 65.0.3325.162 Channel: n/a OS Version: 10.0 Flash Version: One observation, When opens application in chrome browser along with fiddler, which overrides chrome's default proxy servers, calls works properly in that case. It's difficult to understand the event logs, can you please help us out to know the root cause.
,
Mar 27 2018
,
Mar 29 2018
honey.setia@ Could you please help us with the sample html test case & expected behavior for further triage from TE
,
Apr 2 2018
@kkaluri thanks for your reply. Will not be possible to share the sample as issue only occurred on our intranet application. Appreciate if you can extract any info from attached dump if possible and share. That will be helpful to further debugging the issue.
,
Apr 2 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 5 2018
honey.setia@ Thanks for the update. As per comment #4, any information cannot be extracted from the attached file in comment #1 at TE end. Hence adding TE-NeedsTriageHelp label and requesting someone from Internals>Network team to look into this issue and help in further triaging. Thanks..
,
Apr 10 2018
We analysed issue further and found request is failing with ERR_UNEXPECTED error when Chrome trying to authenticate a request. We are using SPNEGO kerberos in our application.
,
Apr 17 2018
Hey honey.setia, would you mind uploading a new netlog per https://dev.chromium.org/for-testers/providing-network-details, the one you uploaded is failing to parse in chrome://net-internals#import, and has no mention of ERR_UNEXPECTED.
,
Apr 18 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 18 2018
This looks like a bug in the auth logic, combined with a server bug. We connect to the server, get a negotiate auth challenge, re-send the request with credentials, and then the server hangs up on us. The auth code tries to parse the next round of the auth challenge (I assume), gets confused, and returns ERR_UNEXPECTED, instead of ERR_CONNECTION_CLOSED, which is how the request probably should fail. The fact that the request is failing does look to be the server's fault, unless there's something wrong with the auth credentials we send.
,
Apr 25 2018
,
Apr 25 2018
[xunjieli]: Here's the auth bug I mentioned - the weird thing is the ERR_UNEXPECTED that we return, instead of ERR_CONNECTION_CLOSED, and I suspect that's a bug in one layer (Probably HttpProxyClientSocketWrapper, though possibly above or below it) passing the error into the auth code, which then eats it in favor of a less useful error message. The fact that the server is hanging up on is is presumably a server bug or network issue - even if we gave bad credentials, it should at least be returning an error page. Anyhow, this seems like a low priority bug, just suggesting it as a way to get your hands into the auth code with an issue I think is tractable. |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by honey.se...@gmail.com
, Mar 27 201852.8 KB
52.8 KB View Download