[ https://issues.apache.org/jira/browse/KNOX-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905467#comment-15905467 ]
Sumit Gupta commented on KNOX-897: ---------------------------------- Ah I missed that! Thanks for pointing that out [~smore]. Sorry for the extra investigation here but I thought we were potentially missing out on a use case. I think this JIRA can go back to being resolved! > X-Forwarded-Port is incorrectly determined > ------------------------------------------ > > Key: KNOX-897 > URL: https://issues.apache.org/jira/browse/KNOX-897 > Project: Apache Knox > Issue Type: Bug > Affects Versions: 0.11.0 > Reporter: Attila Kanto > Fix For: 0.12.0 > > Attachments: gateway.log, knox-897.patch, Screen Shot 2017-03-01 at > 14.44.03.png > > > If the client fills out the following headers: > {code} > Header[X-Forwarded-Host]=local.somehost.com > Header[X-Forwarded-Proto]=https > {code} > 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). -- This message was sent by Atlassian JIRA (v6.3.15#6346)