Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #2503

Closed (moved)
(moved)
Open
Created Feb 07, 2011 by Robert Ransom@rransom

Tor describes HTTPS proxy 403 errors as 'unexpected status code'

When Tor tries to connect to a relay or bridge through an HTTPS proxy, and the CONNECT request is rejected with a 403 error code (meaning 'Forbidden'), Tor describes the 403 response as an 'unexpected status code'. 403 errors should be logged with a more correct/useful message, and there are probably other error codes we should describe better as well.

For 403 errors, we could log "... proxy refused to allow connection to %s".

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking