You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
"Block all HTTP requests" blocks requests even to localhost #2323
Localhost refers to the 127.0.0.1 loopback interface, therefore no data is ever leaving the network. Including it in the "block all HTTP requests" makes it needlessly harder to interact with local webservers.
I've closed issues #9142 and #13511 as duplicates of this issue, though those issues are about allowing unencrypted requests to RFC1918 private addresses and not localhost 127.0.0.1/8. If a fix for this issue is limited to just localhost, then one of those issues should be reopened or a new issue should be created to cover other private address ranges.
Activity
semenko commentedon Dec 17, 2015
Going to close as wontfix for now.
Feel free to send a PR to fix, but this adds a fair amount of complexity if we try to deal with localhost 127.0.0.0/8 resolution, etc.
mweitzel commentedon Dec 25, 2015
What about an HTTP-OK whitelist? That would resolve this without it being a special case fix.
semenko commentedon Dec 27, 2015
Ok, rethinking this, I like it. I'll try to integrate it, at least in Chrome, with the overhaul of the extension.
Chrome trusts these origins, which we should whitelist (if we see them in webRequest):
per https://www.chromium.org/Home/chromium-security/security-faq#TOC-Which-origins-are-secure-
Bisaloo commentedon Mar 4, 2017
@Hainish, what's the status of this after 1dafcc9?
jeremyn commentedon Nov 7, 2017
I've closed issues #9142 and #13511 as duplicates of this issue, though those issues are about allowing unencrypted requests to RFC1918 private addresses and not localhost 127.0.0.1/8. If a fix for this issue is limited to just localhost, then one of those issues should be reopened or a new issue should be created to cover other private address ranges.
Hainish commentedon Sep 7, 2018
This is no longer the case, closing. Thanks!