Opened 6 years ago

Last modified 2 years ago

#11869 new defect

HTTPS Everywhere conflicts with other extensions like Tampermonkey

Reported by: Frederick888 Owned by: zyan
Priority: Low Milestone:
Component: HTTPS Everywhere/EFF-HTTPS Everywhere Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


HTTPS Everywhere: 2014.4.25 for Chrome

Chrome: 34.0.1847.131 (Official Build 265687) for Windows


It seems that what HTTPS Everywhere does is to "redirect" the address to the https attached one. But this doesn't work with some extensions.

For example, if a URL of a script in Tampermonkey matches a rule of HTTPS Everywhere, it will prevent the script from running normally.

My situation was that, I inserted a line of


into my script, so that the script cannot fetch the js file normally.

Child Tickets

Change History (3)

comment:1 Changed 6 years ago by zyan

Priority: normalminor

We have seen this with My understanding is that when multiple extensions use the webrequest listeners to modify requests, there is some arbitrary order in who gets to do it. Not sure that there's anything we can do about it at the moment.

comment:2 Changed 6 years ago by derjanb

Hi, this is the Tampermonkey dev.

If this becomes important HTTPS Everywhere could offer an inter-extension communication API so that TM would send some URLs it wants to load and HTTPS Everywhere replies with maybe modified URLs that TM should load.



comment:3 Changed 2 years ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

Note: See TracTickets for help on using tickets.