Skip to content

FIX login page fails when server non http/s ports#14

Open
quorauk wants to merge 1 commit intoUKGovLD:masterfrom
quorauk:master
Open

FIX login page fails when server non http/s ports#14
quorauk wants to merge 1 commit intoUKGovLD:masterfrom
quorauk:master

Conversation

@quorauk
Copy link

@quorauk quorauk commented Jun 5, 2019

resolves #13

@der
Copy link
Contributor

der commented Jun 11, 2019

This could be appropriate for some specific deployments but it depends on the front end proxy configuration. In particular the report for the request at it arrives at tomcat may or may not be the same as the external port depending on connector used (ajp or http) and may or may not be rewritten by the proxy.

I suspect the only robust solution would be some explicit configuration, e.g. in the config part of app.conf.

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.

Login page redirects to port 80 regardless of port registry is on

2 participants