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
{{ message }}
This repository has been archived by the owner on Apr 18, 2018. It is now read-only.
pushmanager has the capability to generate links to itself, but it uses the server and port it has bound to in order to generate those links. When pushmanager is run behind a proxy, the port it binds to and the port that users use to access it (i.e. the port the proxy binds to), are not the same.
When I've dealt with this issue in other proxied webapps, I have added configuration knobs that allow me to inform the app "bind to this host and port, but generate links for this host and port". Typically I would then set the webapp to bind to "127.0.0.1:" when run in production.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
pushmanager has the capability to generate links to itself, but it uses the server and port it has bound to in order to generate those links. When pushmanager is run behind a proxy, the port it binds to and the port that users use to access it (i.e. the port the proxy binds to), are not the same.
When I've dealt with this issue in other proxied webapps, I have added configuration knobs that allow me to inform the app "bind to this host and port, but generate links for this host and port". Typically I would then set the webapp to bind to "127.0.0.1:" when run in production.
The text was updated successfully, but these errors were encountered: