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
  • #25434

Closed (moved)
(moved)
Open
Created Mar 06, 2018 by David Fifield@dcf

Use `ListenAndServeTLS`, not separate `listenTLS` and `Serve` in snowflake-server

Port these two patches from meek-server to snowflake-server:

  • Use ListenAndServe{TLS} rather than separate Listen and Serve.
  • Wait briefly after calling ListenAndServe{TLS} to see if it errors. This way, we automatically get support for HTTP/2 and whatever TLS settings Go configures by default, rather than copy-pasted settings from some previous version. The only thing we lose is the ability to run a server on port 0; i.e. a random ephemeral port.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking