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 Oct 20, 2024. It is now read-only.
I would love to support that, however at the time there isn't really the
resources of time to do this. I am very busy in the foreseeable future,
but would love to accept contributions if you are willing.
I can't promise a commitment just yet, but if we need to support more of this type of thing in one of our applications I will spend some time and see if I can put together a pull request.
I can't promise a commitment just yet, but if we need to support more of
this type of thing in one of our applications I will spend some time and
see if I can put together a pull request.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-15187696
.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For a site using the reverse proxy
RewriteRule http://www.example.com/proxysite(.*) http://examplesite.reallocation.com$1 [P]
When the html contains /path/tolocation it will result in a 404 because it instead points to http://www.example.com/path/tolocation instead of http://www.example.com/proxysite/path/tolocation
Any other creative ways to deal with this type of setup without having to modify the html?
The text was updated successfully, but these errors were encountered: