Conflicts with https everywhere

[michaldybczak]

Description

I got notification about extension error on google chrome. I went to extension page and I saw this error message (translated roughly from my native language):

Extension didn't redirect web call to https://domain.com/ads.html because other extension (HTTPS Everywhere) redirected it to https://www.domain.com/ads.html.

Here is the screen:

Expected Behavior

No errors.

Actual Behavior

As described above

Steps to Reproduce

I've been running ghostery with HTTPS Everywhere since few weeks and this error showed just now, so I'm not sure how to reproduce it. I don't get it (so far) on Chromium although I have synced it with the same account.

Versions

• Browser: Google Chrome 63.0.3239.132 (64-bit)
• OS: Manjaro Linux
• Node:?
• NPM:?

[trickpattyFH20]

looking at the the webRequest API docs, it seems like this might not be fixable.
https://developer.chrome.com/extensions/webRequest#implementation

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.

based on this superuser discussion It seems like one potential workaround could be to exclude specific domains from HTTPS Everywhere.

does anyone have any other ideas on how to address this? @jsignanini @chrmod @christophertino ?

[ghostwords]

This sounds like the same issue as EFForg/https-everywhere#14961 (comment).

[michaldybczak]

Yes, it looks like this is the same issue and it was posted 8 days sooner and has more attention so I guess my thread can be closed. There is no need to duplicate topics and it's better to focus on one.

The error message happens rarely (I've seen it twice so far) and it doesn't affect any functionality so it's not a big problem but as stated on the other thread, chrome error messages are raising a red flag and the error is applied to ghostery so it doesn't look good.

P.S. Please, reopen it if it turns out to be a different bug.