New issue
Advanced search Search tips

Issue 821042 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

chrome.webRequest.onHeadersReceived not normalising initiator URL

Reported by k...@kzar.co.uk, Mar 12 2018

Issue description

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

Steps to reproduce the problem:
1. Install the attached extension
2. Inspect the background page of it
3. Browse to https://regex101.com/ in a new tab

What is the expected behavior?
Nothing is logged to the background page

What went wrong?
Something is logged to the background page: "url https://regex101.com/ initiator https://regex101.com normalisedInitiator https://regex101.com/"

Notice that the details.initiator URL is not the same as the normalised initiator URL nor details.url.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 65.0.3325.146  Channel: stable
OS Version: 
Flash Version: 

This is relevant to Adblock Plus, see https://issues.adblockplus.org/ticket/5241 and https://bugs.chromium.org/p/chromium/issues/detail?id=805649
 
initiator-url-test.zip
986 bytes Download
Labels: Needs-Triage-M65

Comment 2 by mattm@chromium.org, Mar 12 2018

Components: Platform>Extensions>API
Cc: vamshi.kommuri@chromium.org
Labels: Needs-Feedback Triaged-ET
Unable to reproduce the issue on reported chrome version 65.0.3325.146 using Ubuntu 14.04 with the below mentioned steps.
1. Launched Chrome
2. Downloaded the file "initiator-url-test.zip" and installed the extension.
3. Navigated to https://regex101.com/ and inspected the page.
Attaching the screen cast of the same.

@Reporter: Could you please have a look at the screen cast and let us know if anything missed from our end. As we are not very clear about Point no.2 in comment#0 i.e., what specific page does "background page" mean, it would be highly helpful if elaborated on it. Any further inputs from your end may help us.

Thanks!
821042.mp4
1.9 MB View Download

Comment 4 by k...@kzar.co.uk, Mar 13 2018

In the screen cast you appear to be opening the console for  https://regex101.com/ instead of the extension.

To open the console for the extension (aka inspect its background page) you do the following:

 1. Navigate to the extensions page chrome://extensions/
 2. Ensure the "Developer mode" toggle on the top right is enabled.
 3. Locate the extension in the page and select "Inspect views
background page" for it.
Project Member

Comment 5 by sheriffbot@chromium.org, Mar 13 2018

Labels: -Needs-Feedback
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

Comment 6 by k...@kzar.co.uk, Mar 13 2018

Sebastian and I looked into this and realised that the initiator is not the full URL but just the origin (e.g. protocol + host). You can close this issue, but you might consider making this clearer in the API documentation.

Sorry for wasting your time, Dave.
Status: WontFix (was: Unconfirmed)
As per comment#6 from the reporter, closing this issue and marking it as Won't fix.

Sign in to add a comment