Possibility of redirecting by specifying an abnormal port.

[kmabashi]

https://github.com/grails/grails-core/blob/f417f92076f1329f09bc44d34d45e4739d5244ad/grails-web-common/src/main/groovy/org/grails/web/servlet/mvc/GrailsWebRequest.java#L471-L474

In the above method, if "X-Forwarded-Proto" is given to the request header, the process does not give the port to the URL. As a result, the port number is arbitrarily removed from the redirect destination URL specification (HTTPheader.location) after login only when the application (Rundeck) accesses via AWS's ALB. Various problems are occurring in the application, such as login failures and CORS violation errors in client-side js. Is it possible to fix this?

AWS ALB automatically adds "X-Forwarded-Proto" to the HTTP header as officially stated.
https://docs.aws.amazon.com/ja_jp/elasticloadbalancing/latest/application/x-forwarded-headers.html

As a proposal for improvement, ALB also provides "X-Forwarded-Port". I have confirmed that the "X-Forwarded-Port" is 4440 for HTTP access to Rundeck via ALB. If this "X-Forwarded-Port" is in the HTTP header, how about modifying it to add it to the URL?

Please consider it.