[ https://issues.apache.org/jira/browse/KNOX-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15903381#comment-15903381 ]
ASF subversion and git services commented on KNOX-897: ------------------------------------------------------ Commit 3ee68053e7d41d3aa6e8777e5e599596fc7ce6a1 in knox's branch refs/heads/master from [~moresandeep] [ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=3ee6805 ] KNOX-897 - X-Forwarded-Port incorrectly defaults to the one configured for Knox if standard ports (80 and 443) are used (Attila Kanto via Sandeep More) > 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 > 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)