New issue
Advanced search Search tips

Issue 777392 link

Starred by 5 users

Issue metadata

Status: Fixed
Owner:
Closed: Feb 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

DevTools: requestIntercepted and requestWillBeSent disagree on Referer header

Reported by sebast...@madumbo.com, Oct 23 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36

Steps to reproduce the problem:
1. Connect to chrome instance with devtools protocol.
2. Set Network.setRequestInterception(true) (https://chromedevtools.github.io/devtools-protocol/tot/Network/#method-setRequestInterception)
3. Watch the requests with Network.continueInterceptedRequest, they lost their Referer header.

What is the expected behavior?
Requests should have the Referer header.

What went wrong?
You can find more informations on the corresponding issue in Puppeteer https://github.com/GoogleChrome/puppeteer/issues/469. 

Some explanations are given there: https://github.com/GoogleChrome/puppeteer/issues/469#issuecomment-324171034

Did this work before? N/A 

Chrome version: 61.0.3163.100  Channel: stable
OS Version: 16.04
Flash Version:
 
Owner: caseq@chromium.org
Status: Assigned (was: Unconfirmed)
Summary: DevTools: requestIntercepted and requestWillBeSent disagree on Referer header (was: DevTools protocol interception setRequestInterception strips the Referer header.)
Issue is not specific to Linux, I'm seeing same issue on Windows 7

Comment 4 by caseq@chromium.org, Feb 7 2018

Status: Fixed (was: Assigned)

Sign in to add a comment