Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

URL suffix for websocket API? #85

Closed
jamieshaw opened this issue Apr 17, 2018 · 2 comments
Closed

URL suffix for websocket API? #85

jamieshaw opened this issue Apr 17, 2018 · 2 comments

Comments

@jamieshaw
Copy link

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:

ProxyPass /hb/websocket wss://localhost:8123/hb/websocket
ProxyPassReverse /hb/websocket wss://localhost:8123/hb/websocket

Without this path, it's impossible to filter the websocket. 👍

@oznu oznu closed this as completed in 939c23c Apr 19, 2018
@oznu
Copy link
Member

oznu commented Apr 19, 2018

Added prefix wsocket. Make sure you proxy the ?token=xxx as well.

@jamieshaw
Copy link
Author

jamieshaw commented Apr 19, 2018

Thanks — confirmed that's working now. (Token doesn't need proxying, is handled by the redirect 👍)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants