-
-
Notifications
You must be signed in to change notification settings - Fork 118
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
Redirects not handled correctly #57
Comments
My upstream server automatically requires most URLS to end with a trailing slash My temporary fix is to use the built in regex rewrites that are built-in with this package:
|
Thanks for the report @anthonysutardja! I'm a bit busy lately so if you could write a test to reproduce your problem it would be very helpful. Let me know if you need some guidance. Thanks again! |
Hello @anthonysutardja I want to address that before 0.9.8. I little help would be really appreciated! Cheers! |
Closed for lack of info. |
Same bug here :( Instead of page being loaded I get 301 redirect to an upstream url. Try with domain https://15min.lt as an upstream. |
301 Redirects by the upstream server causes the proxied url to redirect to the upstream path, rather than the proxied path + upstream path.
The text was updated successfully, but these errors were encountered: