[tor-bugs] #4603 [Tor Browser]: Lower HTTP Keep-Alive limit

[Tor Bug Tracker & Wiki]

#4603: Lower HTTP Keep-Alive limit
---------------------------------------------+------------------------------
 Reporter:  mikeperry                        |          Owner:  mikeperry                    
     Type:  defect                           |         Status:  new                          
 Priority:  major                            |      Milestone:  TorBrowserBundle 2.2.x-stable
Component:  Tor Browser                      |        Version:                               
 Keywords:  MikePerryIterationFires20111211  |         Parent:                               
   Points:                                   |   Actualpoints:                               
---------------------------------------------+------------------------------
Changes (by mikeperry):

  * keywords:  => MikePerryIterationFires20111211


Comment:

 In fact, the keep alive timeout already is a function of time since last
 socket read (see nsHttpConnection::OnSocketReadable and follow
 mLastReadTime around to other functions). I think this means we can safely
 set it very low and still get performance benefits while limiting
 linkability.

 It is somewhat hard to tell for sure that the code can properly handle the
 case where we get *no* data in the keepalive timeout timeframe, but the
 comment in nsHttpConnection::OnInputStreamReady() makes me think it can,
 as does testing with a timeout of 1 second against a image-heavy site over
 Tor.

 So, how low should we go?

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/4603#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online