Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • 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
  • #22407
Closed (moved) (moved)
Open
Issue created May 26, 2017 by Nick Mathewson@nickm🐉

Support HTTP CONNECT tunnels as an alternative to SOCKS

Note: This is NOT a ticket about adding a caching or rewriting or privacy-enhancing HTTP proxy to Tor.

We may want to support the "HTTP CONNECT" command as an alternative to SOCKS, since a fair number of applications support the former but not the latter. For the current definition of HTTP CONNECT, see RFC 7231.

Our existing HTTP parsing code should be sufficient to handle these requests, though we would want to make sure we got the semantics right.

The flexibility of HTTP could make this an alternative to proposal 229.

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