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

Re: [tor-bugs] #3665 [TorBrowserButton]: SafeCache policy has corner cases

#3665: SafeCache policy has corner cases
----------------------------------------+-----------------------------------
 Reporter:  mikeperry                   |          Owner:  mikeperry                    
     Type:  defect                      |         Status:  needs_information            
 Priority:  critical                    |      Milestone:  TorBrowserBundle 2.2.x-stable
Component:  TorBrowserButton            |        Version:                               
 Keywords:  MikePerryIteration20110814  |         Parent:                               
   Points:  6                           |   Actualpoints:                               
----------------------------------------+-----------------------------------
Changes (by mikeperry):

  * status:  new => needs_information


Comment:

 Ok, I committed a change with the loadGroup fix as well as a hack to use
 the referer host if we have neither loadGroup nor notificationCallbacks..

 It solves all of the test cases above, but I'm not sure if the referer
 property is present in the channel for http->https sourcing.. Any test
 cases of that? If we get lucky, it might be present but not transmitted.
 From reading
 https://developer.mozilla.org/en/XPCOM_Interface_Reference/nsIHttpChannel
 it sounds like we won't get lucky... But is there anything else we can do?

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