Mihai Parparita 2990c2b1cf control/controlhttp: use secure WebSockets protocol by default ... Forcing the insecure protocol (and perserving the port number) is only desired for localhost testing, in prod we need to use wss:// to avoid mixed-content errors. Signed-off-by: Mihai Parparita <mihai@tailscale.com>		2022-06-08 15:29:21 -07:00
..
client_js.go	control/controlhttp: use secure WebSockets protocol by default	2022-06-08 15:29:21 -07:00
client.go	control/controlhttp: allow client and server to communicate over WebSockets	2022-06-02 21:20:54 -07:00
constants.go	control/controlhttp: allow client and server to communicate over WebSockets	2022-06-02 21:20:54 -07:00
http_test.go	control/controlhttp: don't assume port 80 upgrade response will work	2022-04-28 09:14:41 -07:00
server.go	net/wsconn: remove homegrown wrapper for turning a websocket.Conn into a net.Conn	2022-06-07 09:28:56 -07:00