Closed Bug 1268370 Opened 10 years ago Closed 10 years ago

Allow to apply "chrome.webRequest" filters for about: URIs

Categories

(WebExtensions :: Untriaged, defect)

defect
Not set
normal

Tracking

(firefox49 affected)

RESOLVED WONTFIX
Tracking Status
firefox49 --- affected

People

(Reporter: yuki, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

For enterprise use I developed an addon to block loading of "about:config". I've tried to migrate the addon from XUL-based to WebExtensions but it is impossible, because "about:" URIs cannot be ooerated by "chrome.webRequest" APIs. Steps to reproduce: 1. Ctrl-Shift-J to open the browser console. 2. Install the addon attached. Actual result: Errors are reported with the message: "Invalid match pattern: 'about:config'" Expected result: No error, and "about:config" is blocked as expected.
Summary: Allow to apply filters for about: URIs → Allow to apply "chrome.webRequest" filters for about: URIs
The source: manifest.json ------------------------------------------ { "manifest_version": 2, "name": "Disable about:config", "version": "2.0a1", "description": "Disable about:config.", "applications": { "gecko": { "id": "disableaboutconfig@clear-code.com", "strict_min_version": "48.0a1" } }, "background": { "scripts": [ "background/blocker.js" ] }, "permissions": [ "webRequest", "webRequestBlocking", "about:config" ] } ------------------------------------------ background/blocker.js ------------------------------------------ /* # This Source Code Form is subject to the terms of the Mozilla Public # License, v. 2.0. If a copy of the MPL was not distributed with this # file, You can obtain one at http://mozilla.org/MPL/2.0/. */ chrome.webRequest.onBeforeRequest.addListener( function(aDetail) { return { redirectUrl: 'data:text/plain,' }; }, { urls: [ 'about:config' ] }, [ 'blocking' ] ); ------------------------------------------
Otherwise I need something new API to control availability of Firefox's configuration feature. MCD (Mission Control Desktop) provides ability to lock specified preferences, but it is nonsense to lock all preferences for the purpose.
webrequests accessing about:URL's is a huge security risk that we are not implementing
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Then, how we disable about:config in enterprise use?
I've opened another bug 1271367 to report the essential problem of this bug.
Product: Toolkit → WebExtensions
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: