chrome.webRequest.onBeforeRequest doesn't intercept WebRTC requests
|Reported by d...@adblockplus.org, Apr 3 2017||Back to list|
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.
Apr 3 2017,
Apr 4 2017,
Apr 12 2017,
We've wrapped RTCPeerConnection in Adblock Plus in the mean time. Some links: - https://adblockplus.org/development-builds/new-filter-type-option-for-webrtc-connections - https://hg.adblockplus.org/adblockpluschrome/rev/06ec9ec7539e
Apr 27 2017,
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.
May 11 2017,
Is this still beinng worked on ?
Visiting http://readcomics.website/ 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