-
Notifications
You must be signed in to change notification settings - Fork 108
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
[BUG] Redirects behind Sub-domain proxy are not working #39
Comments
Hi @Ponkhy, I do not personally use Kutt or Zipline, can you provide a few examples of such redirection error and what they are suppose to redirects to? (Like the initial URL, the invalid redirected URL and the URL suppose to be redirected to and any info you think relevant / will help with our debugging) It would be nice if you could include the browser network tracing dump as well if you know how to generate one. Thanks for raising this issue! |
Hey @tobychui, for some weird reason it seems to work now with Zipline, but it still remains with Kutt. Shorten URL: https://url.myon.lu/nuxy Network Trace (.har): https://cloud.myon.lu/f/f58a79be003f474daf70/ Many thanks! |
Hey, I roughly tested the latest commit 70adadf and it indeed seems to fix this problem. Many thanks! |
Fixed in v2.6.6 |
Describe the bug
It seems like redirects behind a sub-domain proxy are not working properly. I have two services running behind the reverse proxy Kutt and Zipline, both have url short/redirect functions.
If a user tries to open a shorten url of either service, it does change the path behind the domain, but not the domain it should redirect to, that leads to 404 and other errors.
I haven't found anything to adjust the header or behavior.
Expected behavior
The user should be redirected to the appropriate site.
Host Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: