This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-13
Channels
- # admin-announcements (1)
- # beginners (10)
- # boot (15)
- # cider (9)
- # clara (195)
- # cljsrn (24)
- # clojars (20)
- # clojure (46)
- # clojure-android (1)
- # clojure-germany (15)
- # clojure-greece (16)
- # clojure-nl (1)
- # clojure-russia (13)
- # clojure-spec (28)
- # clojure-uk (44)
- # clojurescript (104)
- # clojurex (1)
- # component (7)
- # css (2)
- # cursive (27)
- # datomic (92)
- # dirac (12)
- # emacs (5)
- # lambdaisland (3)
- # lein-figwheel (36)
- # mount (87)
- # off-topic (8)
- # om (102)
- # om-next (3)
- # onyx (30)
- # pedestal (3)
- # re-frame (26)
- # reagent (20)
- # robots (4)
- # specter (18)
- # spirituality-ethics (1)
- # untangled (127)
- # yada (11)
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.
looks like nginx could do that: https://github.com/nicokaiser/nginx-websocket-proxy/blob/master/simple-wss.conf
and btw. I think chrome has some knobs to disable that "localhost was loaded over HTTPS…” restriction for development
@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 ?