Https-everywhere: Don't mess with localhost URLs

Created on 24 Jan 2017  ·  11Comments  ·  Source: EFForg/https-everywhere

With "block all unencrypted requests" enabled, HTTPS Everywhere tries to rewrite localhost URLs to use HTTPS, which is unideal. We probably shouldn't do that.

Also relevant: https://www.w3.org/TR/secure-contexts/#localhost

Most helpful comment

+1 👍 - For all the web developers out there.

All 11 comments

+1 👍 - For all the web developers out there.

+1
Really annoying that it messes with localhost

Affects both, http://127.0.0.1:<PORT> as well as http://localhost:<PORT>.
Pretty annoying.

https://github.com/EFForg/https-everywhere/blob/9a243c6cd71f612a5b539c83f59a469eb5950fae/rewriter/rewriter.js#L69 looks like the line in question.

At this point I would long have changed the regex to use RegExp … so it is possible to break it into smaller part, concatenate it and pass it to new RegExp().

Please stop commenting with +1s; it generates a lot of spam for subscribers/watchers.

@Ryuno-Ki you should PR!

@strugee I have no experience with browser add-ons and would need some guidance for setting up dev environment and testing my patch.

@Ryuno-Ki https://github.com/EFForg/https-everywhere#getting-started has some instructions for getting started with HTTPS Everywhere development. I've only dabbled in HTTPS Everywhere development but I'd be happy to try and help, or I'm sure you could ping one of the core developers.

@Ryuno-Ki Let me know if you plan to PR, otherwise I can add a localhost exception.

I am not sure this is fixed or has been reintroduced as HTTPS Everywhere is now conflicting with IPFS Companion using *.localhost addresses and those get https and errors when EASE mode is enabled.

@Mikaela Please don't bump old issues if possible. Create a new issue instead. Thanks for reporting the issue though, this will be looked into.

Was this page helpful?
0 / 5 - 0 ratings