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 91
    • Issues 91
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 7
    • Merge requests 7
  • 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
  • #29125
Closed
Open
Issue created Jan 18, 2019 by David Fifield@dcfOwner

Make websocket server tolerant of HTTP/2

The Snowflake websocket server, inherited from flash proxy, assumes that the incoming http.ResponseWriter implements the http.Hijacker interface, which HTTP/2 connections do not.

It causes a panic in the log when you connect to the server with e.g. curl:

2019/01/18 18:56:29 http2: panic serving X.X.X.X:YYYY: interface conversion: *http2.responseWriter is not http.Hijacker: missing method Hijack

I'm not sure if WebSocket connections from browsers use HTTP/2 yet or not, but in any case we should handle it gracefully.

My first inclination is to see if porting to gorilla/websocket fixes this and legacy/trac#28726 (moved).

Assignee
Assign to
Time tracking