You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This may have the same answer as #81; but is it possible to use a suffix to identify the websocket connection (and perhaps something not along the lines of /api or /websocket?)
I've got this configured on a Mac mini running macOS server, which unfortunately has a cumbersome setup for reverse proxying — it has two apache servers, one that proxies the other.
In order to configure websocket proxying, the former layer has to have a simple ProxyPass applied but has no ability to filter by request URL, so it has to be done globally by the request path like so:
This may have the same answer as #81; but is it possible to use a suffix to identify the websocket connection (and perhaps something not along the lines of /api or /websocket?)
I've got this configured on a Mac mini running macOS server, which unfortunately has a cumbersome setup for reverse proxying — it has two apache servers, one that proxies the other.
In order to configure websocket proxying, the former layer has to have a simple ProxyPass applied but has no ability to filter by request URL, so it has to be done globally by the request path like so:
Without this path, it's impossible to filter the websocket. 👍
The text was updated successfully, but these errors were encountered: