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.

Ruleset is shown as activated even when the request is blocked #12076

Closed

Description

@gloomy-ghost

STR:

  1. Install uMatrix and block all 3rd parties.
  2. Open https://zh.moegirl.org/Mainpage
  3. Check activated rulesets

Expected:
No ruleset should be shown

Actual:
Ruleset for 3rd parties resources are shown
default

Can be reproduced on both Chrome and Firefox

Activity

  1. jeremyn commented on Aug 24, 2017

    @jeremyn
    Contributor

    https://github.com/Synzvato/decentraleyes/issues/148#issuecomment-285121088 might be interesting. It links to https://developer.chrome.com/extensions/webRequest , which under the section "Conflict Resolution" says:

    Only one extension is allowed to redirect a request or modify a header at a time. If more than one extension attempts to modify the request, the most recently installed extension wins and all others are ignored. An extension is not notified if its instruction to modify or redirect has been ignored.

    Here I guess both uMatrix and HTTPS Everywhere are modifying the request -- uMatrix by blocking, HTTPS Everywhere by rewriting -- and uMatrix's action is "winning" but HTTPS Everywhere isn't notified so it still displays the relevant rulesets.

    So in Chrome at least, it may not be possible to do what you want.

  2. numismatika commented on Aug 25, 2017

    @numismatika
    Contributor

    I think this a bigger problem that should be adressed upstream at both browsers root.
    If you have multiple addons interfering and listening to redirects you get a lot of wrong info.
    If you have an Adblocker like UBO, HTTPS-Everywhere & SmartHTTPS, Info Addons like SixOrNot&Cert Patrol and a Privacy aware addon like Decentral Eyes, the state shown by these addons can become wrong rather fast. Not to mention irritating console errors and csp warnings.
    You have blocked requests, rewritten requests and you want to also save the states of those requests before and after the interference so you can properly show info about them.

  3. pipboy96 commented on Mar 28, 2019

    @pipboy96
    Contributor

    This is not possible to fix since HTTPS Everywhere can't know whether the request will be blocked by the others addons you have.

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