Skip to content
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

Fixes redirect bug for reverse proxy #495

Merged
merged 1 commit into from
Nov 2, 2022

Conversation

FingerlessGlov3s
Copy link
Contributor

If you are logged out of XBackbone, and browse to /upload for example the direction holds the request URI, which isn't an issue unless you've got a reverse proxy in front of it. For example, if the app is running in a container on port 8080, and Traefik is doing the reverse proxying, when you try login after being redirected to the login page, the redirectTo session contains the internal port number, which causes you to be redirected to https://mydomain.com:8080/upload instead of the correct https://mydomain.com/upload

If you are logged out of XBackbone, and browse to `/upload` for example the direction holds the request URI, which isn't an issue unless you've got a reverse proxy in front of it.
For example, if the app is running in a container on port 8080, and Traefik is doing the reverse proxying, when you try login after being redirected to the login page, the redirectTo session contains the internal port number, which causes you to be redirected to `https://mydomain.com:8080/upload` instead of the correct `https://mydomain.com/upload`
@sergix44
Copy link
Owner

sergix44 commented Nov 2, 2022

If you are logged out of XBackbone, and browse to /upload for example the direction holds the request URI, which isn't an issue unless you've got a reverse proxy in front of it. For example, if the app is running in a container on port 8080, and Traefik is doing the reverse proxying, when you try login after being redirected to the login page, the redirectTo session contains the internal port number, which causes you to be redirected to https://mydomain.com:8080/upload instead of the correct https://mydomain.com/upload

Nice! 🔝

Did you tested if everything works as expected even for non reverse proxy setups?

@FingerlessGlov3s
Copy link
Contributor Author

Works fine without reverse proxy too 😊

@sergix44 sergix44 merged commit 1e0e549 into sergix44:master Nov 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants