As proposed in my issue ArchiveTeam/seesaw-kit#129, the client-side interactive stuff should behave similar to the assets loaded by the website (js, css, ...). Let SockJS and the browser handle the details.
In a setup where the webinterface is running behind a reverse proxy at a different path, requests done
by the JavaScript go to the wrong path.
(Reverse proxy is setup in a way where the
browser/webserver sees /warrior1/api/stop but seesaw-kit still sees /api/stop.
With a little hack these changes are currently used for my running setup, successfully hosting multiple warriors behind the same host but on different paths.
As proposed in my issue ArchiveTeam/seesaw-kit#129, the client-side interactive stuff should behave similar to the assets loaded by the website (js, css, ...). Let SockJS and the browser handle the details.
In a setup where the webinterface is running behind a reverse proxy at a different path, requests done by the JavaScript go to the wrong path. (Reverse proxy is setup in a way where the browser/webserver sees
/warrior1/api/stopbut seesaw-kit still sees/api/stop.With a little hack these changes are currently used for my running setup, successfully hosting multiple warriors behind the same host but on different paths.