Issue metadata
Sign in to add a comment
|
Chrome doesn't prompt for proxy authentication (NTLM)
Reported by
azura...@gmail.com,
Nov 3 2016
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.87 Safari/537.36 Steps to reproduce the problem: 1. Turn proxy on 2. Open any page What is the expected behavior? Browser prompt for login/password for authentication What went wrong? Browser doesn't prompt for anything and show error invalid handle Did this work before? Yes 53 Chrome version: 54.0.2840.87 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 23.0 r0 I'm admin of proxy. Only one user has this problem. On proxy I see, that proxy sends HTTP 407 code to browser, but Chrome doesn't understand it or ignore (I don't know). I attached net-internals log from user machine.
,
Nov 4 2016
I'm familiar with issue 648366 , had it with other users on Chrome v53, but now error was not the same at first look. Maybe the root cause is the same, I'm not sure. Unfortunatly this issue happened with user, who is travels a lot and I couldn't check if KB3189866 was installed.
,
Nov 8 2016
Can anyone give an update on this issue? Is it the same as Issue 648366 or not?
,
Nov 8 2016
Lopping to few folks who might be aware of.
,
Nov 14 2016
Hey Asanka, is the pending CL on 648366 related to this issue too? I am no expert in this code but it seems related - the Auth is interrupted after the Proxy-Authenticate: NTLM [128 bytes were stripped] response from the server which coincides with the moment where the UAL starts staring at squirrels in the other bug.
,
Nov 14 2016
The pending CL in issue fixes an issue in our state machine where we don't use a fresh credentials handle after the initial handshake fails. The secondary handshake will use explicit credentials and hence needs a new credentials handle. Since the failure in the log at #0 happens on the initial handshake, it's unlikely to be fixed by the pending CL. I'll look at what might be causing this, but so far my attempts at reproducing the issue with different network configurations have failed.
,
Nov 15 2016
,
Nov 16 2016
Adding a blocker label to track the progress on this issue. We can get it merged if its fixed during M55 time frame.
,
Nov 16 2016
,
Nov 16 2016
Folding this into issue 648366 . I need to land one more CL but that would address this case as well. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ligim...@chromium.org
, Nov 3 2016Labels: M-54
Owner: asanka@chromium.org
Status: Assigned (was: Unconfirmed)