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

Issue 707683 link

Starred by 19 users

Issue metadata

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



Sign in to add a comment

chrome.webRequest.onBeforeRequest doesn't intercept WebRTC requests

Reported by d...@adblockplus.org, Apr 3 2017

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:

 - https://github.com/uBlockOrigin/uAssets/issues/251
 - https://issues.adblockplus.org/ticket/4455

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 guidou@chromium.org, 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.
Cc: pkalinnikov@chromium.org

Comment 6 Deleted

Comment 7 Deleted

Comment 8 by sscar...@gmail.com, Nov 18 2017

Is this still beinng worked on ?

Comment 9 by dahann...@gmail.com, Nov 21 2017

any updates?
Visiting http://readcomics.website/ ads are pulled via a WebRTC connection, websites likes these is the reason we need to have bug fixed asap.


In enterprise scenarios, it is vital to be able to monitor the quality of real-time communications. Important metrics would be latency, data volume, and a few others. We would love to implement that kind of capability in our uberAgent product, but we would need to be able to identify WebRTC communications from within an extension.

Sign in to add a comment