Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Ability to prevent connection going through HTTP (clearnet only) #262

Open
za3ter2p opened this issue Jun 13, 2020 · 1 comment

Comments

@za3ter2p
Copy link

Add (Optional) plugin or browser option to lock the connection over TLS rather than falling into the http insecure connection on the clearnet if the website support both connections (http/https).

e.g of plugin doing same effect is HTTPS-Everywhere:

https://www.eff.org/https-everywhere

@za3ter2p za3ter2p changed the title Feature request: Ability to prevent connection going through HTTP Feature request: Ability to prevent connection going through HTTP (clearnet only) Jun 13, 2020
@hrj
Copy link
Member

hrj commented Jun 15, 2020

This is a good idea which has been on my mind for some time. Thanks for raising the issue.

The rough outline of how I expect this feature to work:

  • When user explicitly types a URL with protocol in it, we respect it.
  • When user types a partial URL without protocol, we assume https, rather than http.
  • When user clicks a link with http we don't directly navigate to it, but show a screen that allows the user to switch to https or continue with http.
  • Note that: for resource requests from a page (such as images, etc), the request manager already has support for blocking insecure requests.

PRs welcome.

I am currently focussed on improving the layout engine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants