rgm 2021-04-26T23:09:59.068700Z

so I had the semi-bright idea of using caddy as a proxy in dev, given how easy it makes TLS for local development. I’ve got it going fine for my http-kit ring server (reverse-proxying HTTPS 8443 -> HTTP 8080). I also have a websocket passing successfully through Caddy to my ring server (<wss://>). Figwheel’s giving me trouble though. If I reverse-proxy HTTPS 9501 -> HTTP 9500 and set :connect-url to <wss://>, the default server in Figwheel seems to respond to <wss://> with a 200 and the default HTML page that Figwheel sends out when you don’t have /resources/public/index.html for it to latch on to.

rgm 2021-04-26T23:10:22.069Z

that is, it doesn’t seem to upgrade the … oh, wait a minute.

rgm 2021-04-26T23:13:35.070200Z

:connect-url "<wss://>" DOES work … I had left off the trailing figwheel-connect and was trying to connect to the root / route with a websocket, which is already taken by the default host page that boots the figwheel connection :man-facepalming: .

rgm 2021-04-26T23:15:56.071Z

(half my brain: why didn’t you ask this an hour ago. Other half: then I wouldn’t have been able to explain it clearly enough to spot the issue).

rgm 2021-04-26T23:17:20.071200Z

(stupid brain)