New issue
Advanced search Search tips

Issue 846377 link

Starred by 2 users

Issue metadata

Status: Unconfirmed
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

chrome.webRequest doesn't behave as documented

Reported by nn1436...@gmail.com, May 24 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0

Steps to reproduce the problem:
Navigate to website when proxy with authentication is  configured.

What is the expected behavior?
According to https://developer.chrome.com/extensions/webRequest the events should be:

BeforeRequest
BeforeSendHeaders
SendHeaders
HeadersReceived
AuthRequired
*BeforeSendHeaders*
*SendHeaders*
*HeadersReceived*
ResponseStarted
Completed

What went wrong?
The marked events are not received at all.
The order is:

BeforeRequest
BeforeSendHeaders
SendHeaders
HeadersReceived
AuthRequired
ResponseStarted
Completed

https://imgur.com/a/CG3stLS

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 66  Channel: n/a
OS Version: 10.0
Flash Version: Shockwave Flash 29.0 r0

If this is a new Chrome behavior, then please update the documentation.
 
auth.png
15.3 KB View Download
Labels: Needs-Triage-M66
Components: Platform>Extensions>Documentation

Sign in to add a comment