Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S Snowflake
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 90
    • Issues 90
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 6
    • Merge requests 6
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • Pluggable Transports
  • Snowflake
  • Issues
  • #40005
Closed
Open
Issue created Jul 30, 2020 by Cecylia Bocovich@cohoshOwner

Use of http.DefaultTransport can cause the proxy and clients to hang indefinitely

The http.DefaultTransport leaves ResponseHeaderTimeout unset by default. This means that the proxy and client that use this transport will hang indefinitely if they don't receive a response from the broker. This happens rarely in practice, but we've seen it before with #29861 (closed). A better thing to do is set a long time out and log an error message if contacting the broker failed.

The timeout for clients should be at least as long as the broker's ClientTimeout and likewise the proxies should time out after the broker's ProxyTimeout would be triggered.

Assignee
Assign to
Time tracking