Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • H HTTPS Everywhere
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • HTTPS Everywhere
  • Issues
  • #28383
Closed
Open
Issue created Nov 08, 2018 by Trac@tracbot

HTTPS Everywhere's exceptions persist

Using Tor it is recommended to try secure connections first. Unfortunately HTTPS Everywhere doesn't work this way by default: https://www.eff.org/https-everywhere/faq#why-use-a-whitelist-of-sites-that-support-https-why-cant-you-try-to-use-https-for-every-last-site-and-only-fall-back-to-http-if-it-isnt-available

To try secure connections first, the user has to Disable all unencrypted requests. When HTTPS Everywhere is set to Disable all unencrypted requests, [[span(style=background-color: #FFC8C8, the exceptions (the sites visited via HTTP) persist even after Tor Browser is closed.)]]

When HTTPS Everywhere disabled on a site, Reset to Defaults is not available from the button. To clear the list the user has to open the about:addons page, select HTTPS Everywhere's options and remove sites 1-by-1 from the HTTPS Everywhere Sites Disabled list. There is no "clear all" button.

Trac:
Username: janbhez

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking