dirac

Dirac v1.7.2 is out: https://github.com/binaryage/dirac/releases/tag/v1.7.2
2016-06-13T01:34:29.000005Z

Yeah, it makes a huge difference. Thanks!!

superstructor 2016-06-13T23:16:12.000006Z

@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.”

superstructor 2016-06-13T23:16:54.000007Z

I’ve been looking at dirac.lib.ws-server and dirac.lib.nrepl-tunnel-server to try work out how to implement WSS.

2016-06-13T23:17:18.000008Z

I have no experience with WSS, should be doable IMO

2016-06-13T23:17:37.000009Z

or find a WSS proxy and put it in front of dirac agent

2016-06-13T23:18:42.000010Z

looks like nginx could do that: https://github.com/nicokaiser/nginx-websocket-proxy/blob/master/simple-wss.conf

2016-06-13T23:18:56.000012Z

in theory

2016-06-13T23:22:16.000013Z

and btw. I think chrome has some knobs to disable that "localhost was loaded over HTTPS…” restriction for development

2016-06-13T23:22:25.000014Z

which sounds like easiest solution to me

2016-06-13T23:24:45.000015Z

search for unsafely-treat-insecure-origin-as-secure command-line option

superstructor 2016-06-13T23:56:20.000016Z

@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 ?

superstructor 2016-06-13T23:57:15.000018Z

or, would you prefer that two impls are switchable via config, a http-kit one and a jetty one ?