[Feature Request] Allow Extensions to deactivate prefetch, dns-prefetch, preconnect and/or fire blockable webRequest Events
Reported by
stoical...@gmail.com,
Nov 16 2017
|
||||||||
Issue descriptionSince Chromium Version 51 the chrome.privacy.network.networkPredictionEnabled Setting does no longer affect the behavior of link rel preconnect, prefetch or dns-prefetch - those will always execute and make DNS requests, open sockets and in case of prefetch make a HTTP request. This was changed in Issue 589369 and further discussed in Issue 785125 . For prefetch webRequest Events are fired and it's possible to block these requests. For preconnect and dns-prefetch are no webRequest Events fired and thus there's currently no (known) way to prevent connections/requests in this case. To restore full functionality for extensions that aim to block requests (like e.g. uBlock Origin) a way to disable or block these requests is needed. I would suggest either * Another chrome.privacy.network setting to disable prefetch, preconnect and dns-prefetch and/or * blockable webRequest Events for preconnect and dns-prefetch Thanks for your work and Best regards!
,
Nov 16 2017
Adding a few labels: - It's a feature request for extensions - To control Web behaviour (link-rel & friends are part of HTML) - for privacy reasons Issue 773392 is a request in a similar vein
,
Nov 16 2017
I was just talking with mmenke@ about this in https://chromium-review.googlesource.com/c/chromium/src/+/775141 (which updates the documentation for networkPredictionEnabled). Overall, I think this is fairly reasonable. rsleevi@, do you know how difficult this would be from a technical perspective? Do we already have any kind of setting to disable prefetch?
,
Nov 16 2017
We'd probably need to make the change in blink, rather than in the browser process, since the network stack is moving out of process, and shouldn't know anything about web APIs. So probably best to ask someone more familiar with that side of things.
,
Dec 8 2017
Assigning to sockets_tcp OWNERS as the crash seems to be originating from sockets_tcp api.
,
Dec 8 2017
Ugg, my bad, was meant to update other bug x(
,
Jan 12 2018
,
Jan 14
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 14
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by mmenke@chromium.org
, Nov 16 2017Components: Platform>Extensions>API
Labels: -Type-Bug Type-Feature
Status: Untriaged (was: Unconfirmed)