You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Attila Kanto (JIRA)" <ji...@apache.org> on 2017/03/01 14:03:45 UTC
[jira] [Updated] (KNOX-897) X-Forwarded-Port is incorrectly
determined
[ https://issues.apache.org/jira/browse/KNOX-897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Attila Kanto updated KNOX-897:
------------------------------
Status: Patch Available (was: Open)
Patch:
X-Forwarded-Port is determined from request headers and if it is not available therem, then use default values instead of filling it with local Knox port
> 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, 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)