Dec 10, 2025

I've removed the [socket] endpoint and inherited protocol_explore -> protocol_html -> protocol_ws -> protocol_http -> protocol. Websockets requires underlying http for the "upgrade" handshake, and while not all html sites may use websockets, placing it into the hierarchy simplifies configuration. So there's just a simple bool option to disable the upgrade if not used by the endpoint. So websockets is now enabled on the explore and web endpoints, disabled on web. This means websocket connections are on the same port as the http requests for a given endpoint. I haven't integrated ws dispatch for explore yet thought.