Improve webserver mount-point compatibility (#129)#130
Open
SpraxDev wants to merge 1 commit intoArchiveTeam:developmentfrom
Open
Improve webserver mount-point compatibility (#129)#130SpraxDev wants to merge 1 commit intoArchiveTeam:developmentfrom
SpraxDev wants to merge 1 commit intoArchiveTeam:developmentfrom
Conversation
SpraxDev
changed the title
As proposed in my issue ArchiveTeam#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`.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As proposed in my issue #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.