4

Occasionally, when opening a wikipedia page I get this type of error in Chrome:

Warning: This extension failed to redirect a network request to http://www.wikiwand.com/en/Lymphoma because another extension (HTTPS Everywhere) redirected it to https://en.wikipedia.org/wiki/Lymphoma.

While it seems that it doesn't affect anything significant, it keeps causing me to click the 3-bars button and check the error, which is just annoying.

Any idea how to get rid of this without having to disable my extensions?

Improve this question
6
  • Your Wikiwand and HTTPS Everywhere extensions are conflicting. Either disable one of them, or try excluding Wikipedia from the latter.
    – Karan
    Jun 10, 2015 at 13:20
  • 1
    What part of "rid of this without having to disable my extensions" wasn't clear? :p
    – traveh
    Jun 10, 2015 at 13:23
  • Do the latter then. It's one or the other. If you want to do neither then live with the annoyance, simple.
    – Karan
    Jun 10, 2015 at 13:24
  • 1
    I couldn't find any way to disable domains... do you know how to do it?
    – traveh
    Jun 10, 2015 at 13:25
  • 2
    Create an exclusion ruleset. This should help.
    – Karan
    Jun 10, 2015 at 13:31

1 Answer 1

Reset to default
3

General problem

two (Chrome/Web)-Extensions tried to redirect the same request. In this case

the most recently installed extension wins and all others are ignored.

uBlock (and others) consider this non-fixable on their part, as

An extension is not notified if its instruction to modify or redirect has been ignored.

Your problem

As mentioned, it seems that you can exclude specific patterns from HTTPS Everywhere, as in

<exclusion pattern="^http://(?:\w+\.)?stack(?:exchange|overflow)\.com/users/authenticate/" />

It should be possible to exclude all wikipedia.org links, as the wikiwand extension then redirects to wikiwand.com (if that works), but wikiwand acknowledges:

There are some known problems with those extensions: Kill Evil, HTTPS Everywhere

... but not on the main conflicts list.

It seems as if wikipedia already uses https, so simply excluding wikipedia.org would not pose a problem.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .