New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 752195 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Feature



Sign in to add a comment

Network.requestIntercepted with AuthChallenge is never received through a websocket connection

Reported by heku...@ucdavis.edu, Aug 3 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36

Steps to reproduce the problem:
1. Launch Chrome with a debugging port specified
2. Connected to the debugging port using a websocket connection
3. Call Network.setRequestInterceptionEnabled API to start receiving Network.requestIntercepted events.
4. Go to a webpage that requires HTTP authentications
5. Get all received messages from the websocket and there will be no Network.requestIntercepted event.

My goal is to catch the HTTP authentication via Network.requestIntercepted event and call Network.continueInterceptedRequest with an AuthChallengeResponse argument with username and password for the HTTP authentication.

What is the expected behavior?
Network.requestIntercepted event received with AuthChallenge in the response.

What went wrong?
Network.requestIntercepted events are not received.

Did this work before? No 

Chrome version: 61.0.3163.25 dev  Channel: dev
OS Version: Ubuntu 16.04.1
Flash Version:
 
Labels: Needs-Triage-M61
Labels: TE-NeedsTriageHelp
Cc: tyoshino@chromium.org ricea@chromium.org
Components: Blink>Network>WebSockets
cc'ing , ricea@ and tyoshino@ for further triage of this bug.

Comment 4 by ricea@chromium.org, Aug 7 2017

Components: Platform>DevTools>Network
Status: Untriaged (was: Unconfirmed)
If I understand correctly, this is actually DevTools functionality. Because the WebSocket code hooks the network stack at a low level, it may not actually be possible to support this API.

I have added the DevTools Network component for triage.
Thanks for the response ricea. It seems to work on Mac according to a different post regarding the requestIntercepted API. Are there major differences in the network stack between mac and other platforms?

https://bugs.chromium.org/p/chromium/issues/detail?id=752010#c8

Comment 6 by ricea@chromium.org, Aug 7 2017

Platform differences in the network stack are abstracted away at a low level and almost all code is shared between platforms.

HTTP Basic and Digest authentication work the same on all platforms (except for issues involving platform-specific password storage and UI, which shouldn't be involved here).

Negotiate and NTLM authentication have more platform-specific code, but I know of no reason why that would affect DevTools APIs.
Sounds like it should work for Linux and Windows too then since it's working for Mac according to the other ticket I posted above. 
Owner: allada@chromium.org
Status: Assigned (was: Untriaged)

Comment 9 by heku...@ucdavis.edu, Aug 10 2017

https://bugs.chromium.org/p/chromium/issues/detail?id=752010#c19
I tried to do the same thing as this post since they were able to get the authChallenge response, but it looks like it's not received on Windows or Linux.
Status: WontFix (was: Assigned)
request interception is experimental...

Sign in to add a comment