You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2016/08/02 07:31:20 UTC

[jira] [Resolved] (FELIX-4923) SslFilterResponse doesn 't take in account ssl-forward.header property

     [ https://issues.apache.org/jira/browse/FELIX-4923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved FELIX-4923.
-------------------------------------
    Resolution: Fixed

Thanks for your patch [~asanso]. It's applied

> SslFilterResponse doesn 't take in account ssl-forward.header property
> ----------------------------------------------------------------------
>
>                 Key: FELIX-4923
>                 URL: https://issues.apache.org/jira/browse/FELIX-4923
>             Project: Felix
>          Issue Type: Bug
>          Components: HTTP Service
>            Reporter: Antonio Sanso
>            Assignee: Carsten Ziegeler
>            Priority: Minor
>             Fix For: http.sslfilter-1.0.8
>
>         Attachments: FELIX-4923-patch.txt
>
>
> {{SslFilterResponse}} doesn 't take in account {{ssl-forward}}.header property.
> Indeed the {{SslFilterResponse}} constructor hardcodes {{HDR_X_FORWARDED_PROTO}}.
> {code}
> ...
> request.getHeader(HDR_X_FORWARDED_PROTO);
> ...
> {code}
> the  {{ssl-forward}} osgin configuration should be taken in account IMHO. The default is even different than {{HDR_X_FORWARDED_PROTO}} indeed is rather {{X-Forwarded-SSL}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)