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

Issue metadata

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

Sign in to add a comment

chrome.webRequest.onBeforeRequest doesn't intercept WebRTC requests

Reported by, Apr 3 2017 Back to list

Issue description

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

Steps to reproduce the problem:
1. Create an extension with "webRequest" and "*://*/*" host permissions.
2. Add listener to "chrome.webRequest.onBeforeRequest" in extension's code.
3. Open new tab and perform a WebRTC request to any URL.

What is the expected behavior?
Listener intercepts request.

What went wrong?
Request is sent without interception.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 57.0.2987.133  Channel: stable
OS Version: 
Flash Version: N/A

This is a problem for extensions such as Adblock Plus and uBlock. The lack of API here forces the wrapping of the WebRTC APIs in a content script, not ideal. See related issues:


Note: This issue is very similar to the WebSocket one #129353, so I took most of the description from there.
Labels: Needs-Triage-M57
Components: Platform>Extensions Blink>WebRTC
Labels: TE-NeedsTriageHelp

Comment 4 by, Apr 27 2017

Components: -Blink>WebRTC
Removing Blink>WebRTC component since this seems to be an issue with the extensions mechanism. 
Please re-add the component if the solution to this is it is suspected that the solution is on the WebRTC side.

Comment 6 Deleted

Comment 7 Deleted

Is this still beinng worked on ?
any updates?
Visiting ads are pulled via a WebRTC connection, websites likes these is the reason we need to have bug fixed asap.

Sign in to add a comment