[jira] [Commented] (KNOX-897) X-Forwarded-Port is incorrectly determined

["Sandeep More (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KNOX-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15892754#comment-15892754 ] 

Sandeep More commented on KNOX-897:
-----------------------------------

Hello [~akanto]
Thanks for the patch !
I was going through the documentation for [X-Forwarded-Port| https://knox.apache.org/books/knox-0-11-0/user-guide.html#X-Forwarded-Port] and it states 

bq. The port used in the client request. If this header is passed into Knox its value is maintained, otherwise Knox will populate the header with the value of the port that the request was made coming into Knox.

Looks like your observation are contrary to the above statement (or likely I misread your comment :( ).
Let me know your thoughts !

> 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)