barbaz wrote:Oh... I didn't realize that these requests weren't seen as originating from the webpage.
Yes, they originate from chrome:// URLs.
Could it be useful even for the builtin SYSTEM rule, or are these requests coming from LOCAL (meaning "chrome:" here?) anyway?
EDIT Stupid question, of course the requests are coming from LOCAL if they're indistinguishable from requests made by the browser. Never mind.
No, they're not coming from LOCAL. LOCAL means local addresses; http://192.168.0.1 etc. The internal chrome: protocol is something else entirely.
However, as mentioned above, attempting to block requests from chrome: is not reliable. It may be good as a nuisance blocker, or for getting an idea of what your browser is doing, but a malicious addon could get around it (eg by removing NoScript's hooks).