4697271cef
* [bugfix] send back Sec-Websocket-Protocol header for streaming WebSocket Chrome expects the selected Sec-Websocket-Protocol to be sent back on the WebSocket upgrade request (RFC6455 1.9). * fiddle a bit to avoid getting headers multiple times * add some explanatory notes --------- Co-authored-by: tobi <tobi.smethurst@protonmail.com> |
||
|---|---|---|
| .. | ||
| activitypub | ||
| auth | ||
| client | ||
| fileserver | ||
| health | ||
| metrics | ||
| model | ||
| nodeinfo | ||
| util | ||
| wellknown | ||
| activitypub.go | ||
| auth.go | ||
| client.go | ||
| fileserver.go | ||
| health.go | ||
| metrics.go | ||
| nodeinfo.go | ||
| wellknown.go | ||