@Reporter: Please provide a sample test case/URL using chrome.webRequest.onHeadersReceived API for testing this issue from TE end. Any further information on reproducing the issue will help in triaging the issue in a better way.

Thanks!

I'm pretty sure extensions get both sets of headers.  Note that when we get an authentication challenge, there are no headers from the destination server, until we've authenticated with it, which requires multiple requests.

Hi,

Thanks for your feedback

This is some URLs:
- https://www.parisinfo.com/visiter-a-paris
- https://en.parisinfo.com/
- https://www.amazon.com/Paris-English-subtitled/dp/B01GKTHOPS

When we are behind a proxy, chrome.webRequest.onHeadersReceived received proxy headers instead of server headers. There is no call to onAuthRequired or to onBeforeRedirect listeners.

chrome.webRequest.onCompleted is called with correct headers.but at this stage, we could not modify headers list.

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

khalid.rfk@ - Could you please provide a sample chrome.webRequest.onHeadersReceived API extension file to test the issue from TE-end.
This will help us in triaging the issue further.

Thanks...!!

Of course
Please append the attached crx file to your chrome (see source in zip file) and click on its icon.
This will execute call to test URLs, and show received headers

Note that the problem is when the network is configured with a proxy (blue coat as example)

Thanks.

Deleted: test urls.crx 10.7 KB

test urls.crx 10.7 KB Download

Deleted: test urls.zip 10.5 KB

test urls.zip 10.5 KB Download

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

khalid.rfk@ Thanks for the update.

As per comment #7, as this issue is observed only only proxy. This setup is not available at TE end to test further.
Hence adding Internals>Network>Proxy component and TE-NeedsTriageHelp label for further help in triaging.

Thanks.. 

In this case you are using a connection-based proxy auth scheme (negotate/ntlm).

The expected behavior is that chrome.webRequest.onHeadersReceived() should get called at least twice per request -- once with the headers you noted for the auth challenge, and then subsequently with the target server's response headers.

Can you confirm that you are only getting the first call and never the second?

If so that sounds like a bug with the webRequest integration and and not notifying headers following a transaction restart for auth.

This should be straightforward for a triager to reproduce using a simple proxy server with NTLM.

Yes, we should get call twice, but we receive only the first call, the second is never called