[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #5731 [EFF-HTTPS Everywhere]: [CHROME] conflict with other extensions using WebRequest API (Ghostery, AdBlock Plus, etc)

#5731: [CHROME] conflict with other extensions using WebRequest API (Ghostery,
AdBlock Plus, etc)
----------------------------------+-----------------------------------------
 Reporter:  cerrese               |          Owner:  pde
     Type:  defect                |         Status:  new
 Priority:  major                 |      Milestone:     
Component:  EFF-HTTPS Everywhere  |        Version:     
 Keywords:  conflict              |         Parent:     
   Points:                        |   Actualpoints:     
----------------------------------+-----------------------------------------
Changes (by battre):

 * cc: battre@â (added)


Comment:

 In principle the following conflicts can occur between these extensions:

 1) Extensions try to redirect requests to different destinations.
 2) Extensions try to perform incompatible header modifications.

 @1: A common problem was that HTTPS everywhere redirected a request to an
 https URL, while an AdBlock implementation redirected a request to a
 data:// URL containing a transparent pixel or an empty document. I have
 changed the implementation such that data:// URLs are given precedence
 over other redirects to the network. They do not count as conflicts
 anymore. If two extensions redirect requests to different data:// URLs,
 this is still a conflict.

 @2: There is a lot of logic in Chrome that prevents that identical header
 modifications are not flagged as conflicts. However, if two extensions try
 to set a header to a different value, or if one extension deletes a header
 and the other writes it, this is still considered a conflict.

 I have tried to reproduce your issue but could not. This is how you can
 help debug the problem:

 - Start a recent version of chrome with a new profile directory:
   chrome --user-data-dir=/tmp/temp-profile
   On windows, this would be something like
   chrome --user-data-dir=c:\temp-profile
 - Install the extensions and adblock lists.
 - Restart chrome with
   chrome --user-data-dir=/tmp/temp-profile --log-net-log=/tmp/log.txt
 - Visit the minimal number of pages that trigger the conflict.

 Attach log.txt to this bug or email it to me.

 The first step (creating a new profile directory) is to preserve your
 privacy and make sure that we don't record any background traffic that
 contains personal information.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5731#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs