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
I setup up a reverse proxy to proxy http://mydomain/subway/ to http://localhost:3000, where subway is running; I'm able to request the dir successfully, but all the resources subway requests are unavailable because it's requesting them at root, rather than at /subway/.
i.e. the app should be requesting /subway/socket.io (which works when I test it) , but it's requesting /socket.io .
Ideally, the app would either notice its own URL or allow me to set a configuration option telling it it's at /subway/. (A django app I have running the same way uses the FORCE_SCRIPT_NAME configuration option for this purpose)
Or, is this possible, and I'm missing something?
The text was updated successfully, but these errors were encountered:
I setup up a reverse proxy to proxy http://mydomain/subway/ to http://localhost:3000, where subway is running; I'm able to request the dir successfully, but all the resources subway requests are unavailable because it's requesting them at root, rather than at /subway/.
i.e. the app should be requesting /subway/socket.io (which works when I test it) , but it's requesting /socket.io .
Ideally, the app would either notice its own URL or allow me to set a configuration option telling it it's at /subway/. (A django app I have running the same way uses the FORCE_SCRIPT_NAME configuration option for this purpose)
Or, is this possible, and I'm missing something?
The text was updated successfully, but these errors were encountered: