Skip to content
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
This repository was archived by the owner on Nov 6, 2023. It is now read-only.

Feature request: configuration interface for adding/changing rules. #2283

Closed

Description

@Blaisorblade

Hi! Somehow, http://www.uni-tuebingen.de/en/30477 is available, but HTTPS everywhere redirects me to https://www.uni-tuebingen.de/en/30477 (which isn't available). What's worse, it seems that the only workaround are:

  1. to modify HTTPS Everywhere itself, by modifying it locally or submitting a pull request — unlike, say, adblock tools, there's no way for a user to change the rules.
  2. disable HTTPS Everywhere.
  3. something else I missed because I don't know HTTPS Everywhere well enough.

For the time being, I chose the second solution — I disabled HTTPS Everywhere (temporarily).
Unless the underlying rule is somehow broken, solution 1 doesn't seem plausible — I don't want to submit such a pull request for a single page without any sensitive content, and I believe you shouldn't be reviewing it.
I thought that HTTPS everywhere should notice if a secure page fails loading but the insecure version works, and let me go to the insecure version, but I can see how this would be exploitable.

Hence, can I get a way to add exceptions through a configuration interface?
Or is there some other solution?

Activity

  1. jsha commented on Jul 20, 2015

    @jsha
    Member
  2. Blaisorblade commented on Jul 20, 2015

    @Blaisorblade
    Author

    Hi Jacob! I'm sorry, I've figured from your relevant FAQ entry. This is already better, but the interface still doesn't allow adding exceptions — right now, it seems I could find the rule, copy-paste it and add an exception to the new version. Is that the best way?

  3. Blaisorblade commented on Jul 20, 2015

    @Blaisorblade
    Author

    BTW: should you be interested in feedback on usability, two reasons I got confused were:

    • I looked for Options for this extension, and found none.
    • Not sure why, but I don't find the HTTPS Everywhere logo recognizable, unlike the EFF logo — and the logo of HTTPS Everywhere doesn't fit in with its website (which uses the red-based EFF theme). On the browser bar, I don't even get what it shows — the lock is only visible on the full-size logo on the website.
  4. jsha commented on Jul 20, 2015

    @jsha
    Member

    @Blaisorblade: That's great feedback, thanks! I had a similar issue with the logo(not understanding what it was for) before I started working on the project. It's easy to forget such things as time makes them very familiar.

    For adding exceptions: The best way to do that is to download the source, edit the ruleset in the source, and build your own version / submit the change for acceptance into the plugin. You can also do as you say: Copy the ruleset source into a custom ruleset in your user dir, make the necessary changes, and disable the old ruleset so your new custom ruleset takes control.

  5. J0WI commented on Dec 22, 2017

    @J0WI
    Contributor

    I'm closing this, since we ship with a ruleset editor now: #13560

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions