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

Re: [tor-bugs] #5585 [EFF-HTTPS Everywhere]: [CHROME] CSS content fails to load when appcache is enabled



#5585: [CHROME] CSS content fails to load when appcache is enabled
----------------------------------+-----------------------------------------
 Reporter:  cypherpunks           |          Owner:  pde
     Type:  defect                |         Status:  new
 Priority:  critical              |      Milestone:     
Component:  EFF-HTTPS Everywhere  |        Version:     
 Keywords:                        |         Parent:     
   Points:                        |   Actualpoints:     
----------------------------------+-----------------------------------------

Comment(by pde):

 Replying to [comment:4 isis]:


 >
 > * Make a match rule for !http://*/*.appcache which says to treat the
 parent domain in an "all or nothing" protocol way.

 There isn't really a way to do this with the existing rulesets. We could
 conceivably do it with a combination of new codepaths and some heuristic
 for which rulesets are "partial" and should therefore be disabled if a
 .appcache resource is loaded from that domain. But I feel this is a path
 that leads to dragons.

 At the moment I'm more inclined to ask the Chrome developers for help in
 smoothing out this wrinkle in the WebRequest API. I'm also curious about
 whether they think that clearing the appcache is an acceptable workaround
 in the meantime.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5585#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