New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 759897 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

chrome.webRequest.onBeforeSendHeaders filter for tabId -1 should remove all requests tabId != -1

Project Member Reported by warent@google.com, Aug 29 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36

Steps to reproduce the problem:
1. Use the following code inside of a chrome extension background page:
chrome.webRequest.onBeforeSendHeaders.addListener(
  function(details) {
    if (details.tabId !== -1) {
      console.log("I'm here")
    }
    return { requestHeaders: details.requestHeaders };
  },
  {
    urls: ['https://google.com/*'],
    tabId: -1
  },
  ['blocking', 'requestHeaders']
);

2. Inside any other normal tab:
fetch("https://google.com/")

What is the expected behavior?
background page has nothing logged because the listener should filter out any tabId != -1

What went wrong?
the background page logs "I'm here" because the "tabId: -1" filter does nothing

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 60.0.3112.101  Channel: stable
OS Version: OS X 10.12.6
Flash Version:
 
Cc: brajkumar@chromium.org
Components: Platform>Extensions
Labels: Needs-Triage-M60 Needs-Feedback
warent@ Could you please provide sample extension file as an attachment to check this issue from Chrome-TE end?

Thanks!
Components: -Platform>Extensions Platform>Extensions>API
Labels: -Hotlist-Interop
Cc: ranjitkan@chromium.org
Labels: -Needs-Feedback
Status: WontFix (was: Unconfirmed)
Closing the issue as did not hear back from user again. Please feel free to raise a new issue or reopen if it still persists.

Thanks.!

Comment 4 by warent@google.com, Dec 7 2017

Hi there,

This issue definitely still exists. Please see duplicate: https://bugs.chromium.org/p/chromium/issues/detail?id=612967

Sign in to add a comment