Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #7656

Closed
Open
Opened Dec 06, 2012 by cypherpunks@cypherpunks

Stop automated redundant tor browser requests; disable network.http.connection-retry-timeout

Firefox accelerates HTTP connection timeout. See https://bugzilla.mozilla.org/show_bug.cgi?id=592284

For TorBroswer: No sense to launch parallel connection after 250ms by default, and no logic to tweak it. As long as Tor client retries stream buildings too, any "high" level timeouts makes not so much profit and probably do things much worse. Right now it overloads network and relay exits in first place with waste connection request. TBB must disable it by setting network.http.connection-retry-timeout to 0.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#7656