forked from otalk/otalk-im-client
-
Notifications
You must be signed in to change notification settings - Fork 154
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
Incorrect Relative Paths for Resources - Cannot Reverse Proxy #94
Comments
I made some progress, but it doesn't work that well. It doesn't always go to the right pages, but if you push it here and there it sort of finds its way. Definitely needs some more work.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Kaiwa uses paths relative to root, eg:
This causes a problem when reverse proxying. You can reverse proxy a subdomain just fine, say chat.example.com, because your resources would be at root. However, I don't pay for wildcard ssl, so I want to reverse proxy example.com/chat to example.com:8000. All the paths given by Kaiwa are relative to root, so it's looking for example.com/config.js instead of example.com/chat/config.js.
There is a simple fix for this. Just add a dot in front of every path to make the paths more relative:
I went through the jade views and tried implementing this fix, but it only fixed some minor things like images. Overall the client is still useless when reverse proxied through a non-root path because I can't find all the paths that need fixing.
The text was updated successfully, but these errors were encountered: