Yeah, it makes a huge difference. Thanks!!
@darwin: If we wanted to develop over https
(for testing, not security) is there a way to make the websocket endpoint for the agent SSL as well ? Otherwise we get an error like: “localhost was loaded over HTTP, but attempted to connect to the insecure WebSocket enpoint…This request has been blocked; this endpoint must be available over WSS.”
I’ve been looking at dirac.lib.ws-server
and dirac.lib.nrepl-tunnel-server
to try work out how to implement WSS.
I have no experience with WSS, should be doable IMO
or find a WSS proxy and put it in front of dirac agent
looks like nginx could do that: https://github.com/nicokaiser/nginx-websocket-proxy/blob/master/simple-wss.conf
in theory
and btw. I think chrome has some knobs to disable that "localhost was loaded over HTTPS…” restriction for development
which sounds like easiest solution to me
search for unsafely-treat-insecure-origin-as-secure
command-line option
@darwin: have been looking into a patch and http-kit doesn’t support SSL. Would you be open to a pull request replacing it with jetty ?
or, would you prefer that two impls are switchable via config, a http-kit one and a jetty one ?