New issue
Advanced search Search tips

Issue 646727 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Sep 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

onBeforeSendHeaders not called for requests that required authorization

Reported by sscha...@gmail.com, Sep 14 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.101 Safari/537.36

Steps to reproduce the problem:
1. Create an extension that registers a listener to onBeforeSendHeaders(just log the call) and a listener to onAuthRequired(asyncBlocking).
The Authentication handler just calls the callback and provides the credentials
2. Open a page that requires authorization(response code 401)

What is the expected behavior?
I would expect the listener on onBeforeSendHeaders to be called twice. First there will be a request to the server to which it will respond with 401. At this point the onAuthRequired listener will provide the credentials and another request is made to the server. At this point the onBeforeSendHeaders listener should be called again and the server should respond correctly and send the content of the requested page.

What went wrong?
The onBeforeSendHeaders listener is only called once(for the request with response 401), but is not.

WebStore page: 

Did this work before? N/A 

Chrome version: 53.0.2785.101  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 22.0 r0

I tried to verify that this behavior was also reflected in the developer tools, but it only shows a single request(the request with 401 is not shown there).

To see what really goes on, i used fiddler and saw that there are actually 2 requests(one with response code 401 and one with 200)
 
Project Member

Comment 1 by sheriffbot@chromium.org, Sep 14 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment