Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.11.0
-
None
-
None
Description
If the client fills out the following headers:
Header[X-Forwarded-Host]=local.somehost.com Header[X-Forwarded-Proto]=https
And does not specify the port number in X-Forwarded-Host since it uses the the default port, then Knox automatically populates X-Forwarded-Port header field with its own local port e.g. 8443 instead of the default 443 which results in page not founds (see screenshot and log).