I have a problem getting the websocket part of a route to work. Here is my setup:
- Dockerized web app supporting HTTP and WS (on specific resource)
- Consul service tags for it:
urlprefix-sat-140-patched.applications.fme.lan/
- This web app is scheduled by Nomad
The websocket connection works when accessing the web app directly, but it doesn't work when it is being used through fabio. It looks like the Upgrade response is not taken back to the client. Please see the attached screenshots of the browser's request headers for both direct and fabio-proxied access:
Direct Access:
Fabio Access:
Fabio Routes:
Maybe I am doing something wrong, I am a fabio beginner, but at least I think I have read the relevant documentation. And as it is a tool with (almost) zero configuration overhead I did not need to read much to get most stuff up and running, so thank you for this great addition.
I also tried to add proto=ws to my urlprefix- service tag but that did not help.
Thanks for any help, fix or hint.
I have a problem getting the websocket part of a route to work. Here is my setup:
urlprefix-sat-140-patched.applications.fme.lan/The websocket connection works when accessing the web app directly, but it doesn't work when it is being used through fabio. It looks like the Upgrade response is not taken back to the client. Please see the attached screenshots of the browser's request headers for both direct and fabio-proxied access:
Direct Access:
Fabio Access:
Fabio Routes:
Maybe I am doing something wrong, I am a fabio beginner, but at least I think I have read the relevant documentation. And as it is a tool with (almost) zero configuration overhead I did not need to read much to get most stuff up and running, so thank you for this great addition.
I also tried to add
proto=wsto myurlprefix-service tag but that did not help.Thanks for any help, fix or hint.