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

@RouteURL shouldn't add a port number when it's the default for the protocol #839

Ladicek opened this Issue Nov 6, 2017 · 0 comments


None yet
2 participants

Ladicek commented Nov 6, 2017

The @RouteURL injection always adds a port number to the URL, even if it's the default for given protocol. E.g. instead of, I always get

That's 100% correct, but unexpected. And it actually causes me one issue: in case the route leads to Keycloak and I use it to verify a token that was issued by that Keycloak server, the verification will most likely fail because the token was most likely issued by going through https://sso.server/xxx and not https://sso.server:443/xxx.

@lordofthejars lordofthejars added this to the 1.9.2 milestone Nov 10, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment