feat(caddy): add a WebSockets handler #216
Conversation
sbruens
force-pushed
the
sbruens/caddy-ws
branch
from
23e1d37
to
2f96565
Compare
sbruens
force-pushed
the
sbruens/caddy-ws
branch
from
2f96565
to
21b32cb
Compare
| @@ -10,7 +10,42 @@ | |||
| "apps": { | |||
| "http": { | |||
| "servers": { | |||
| "": { | |||
| "srv0": { | |||
There was a problem hiding this comment.
That's a weird name. Should we call it "main"? Or "primary"?
| "handle": [ | ||
| { | ||
| "handler": "websocket", | ||
| "backend": ":9000" |
There was a problem hiding this comment.
Note that this drops the client IP. We would need something like the PROXY protocol, in which case we should use unix sockets instead of TCP/UDP. But there's a better way.
We should create a a websocket Layer-4 reverse proxy instead, that plugs directly into the layer-4 handler and avoid extra dialing and relaying. It also remove the need for a port.
ws2endpoint can serve as inspiration: https://github.com/Jigsaw-Code/outline-sdk/blob/fe5dc64d1503712f68d53085aa5e53e3d0ea7270/x/examples/ws2endpoint/main.go#L71
Though I see it as being a connection that wraps the http.ResponseWriter and http.Request and is passed to the SS handler.
| case "udp": | ||
| packetDialer := &transport.UDPDialer{} | ||
| endpoint := transport.PacketDialerEndpoint{Dialer: packetDialer, Address: backendAddr.JoinHostPort(0)} | ||
| handler = func(wsConn *websocket.Conn) { |
No description provided.