Opened 8 years ago

Last modified 3 years ago

#7665 new defect

Conflict with 'Do Not Track Me'?

Reported by: cypherpunks Owned by: pde
Priority: Low Milestone:
Component: HTTPS Everywhere/HTTPS Everywhere: Chrome Version:
Severity: Normal Keywords:
Cc: chris.shaffer@… Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Using HTTPS Everywhere 2012.10.31 on Chrome Dev 25.0.1349.2.

Got this warning in a red box in the Chrome extensions settings page:

This extension failed to redirect a network request to,msstotnonly,msstotnmktenus,msstotnlibrollup/1/H.20.3/s7271506283897?AQB=1&ndh=1&t=8/11/2012%2013%3A44%3A15%206%20-480&ns=microsoftsto&pageName=technet%3A/en-us/library/ee958049&g=http%3A// because another extension (DoNotTrackMe) redirected it to chrome-extension://epanfjkfahimkgomnigadpkobaefekcd/webkit/chrome/blank.gif.

Child Tickets

Change History (4)

comment:1 Changed 8 years ago by TheCat

I also show a conflict between these two extensions, with the same error on both "Warning: This extension failed to modify a network request because the modification conflicted with another extension."

comment:2 Changed 8 years ago by TheCat

Cc: chris.shaffer@… added

comment:3 Changed 7 years ago by zyan

Priority: normalminor

Yep, this happens when two extensions try to redirect the same thing. Unfortunately no easy fix.

comment:4 Changed 3 years ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

Note: See TracTickets for help on using tickets.