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

Konrad Windszus updated FELIX-5750:
-----------------------------------
    Description: With the addition of FELIX-5207 and the SSL Filter (described 
in 
http://felix.apache.org/documentation/subprojects/apache-felix-http-service.html#ssl-filter-configuration-properties)
 it seems that there are two different mechanisms in place to actually achieve 
the same. Please clarify in the documentation how these two relate and which 
one to choose for which use case. Even the SSL filter allows to configure the 
headers since https://issues.apache.org/jira/browse/FELIX-4330.  (was: With the 
addition of FELIX-5207 and the SSL Filter (described in 
http://felix.apache.org/documentation/subprojects/apache-felix-http-service.html#ssl-filter-configuration-properties)
 it seems that there are two different mechanisms in place to actually achieve 
the same. Please clarify in the documentation how these two relate and which 
one to choose for which use case.)

> Clarify relation of "Enable Proxy/Load Balancer Connection" Jetty feature and 
> SSL Filter
> ----------------------------------------------------------------------------------------
>
>                 Key: FELIX-5750
>                 URL: https://issues.apache.org/jira/browse/FELIX-5750
>             Project: Felix
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: http.jetty-3.2.0
>            Reporter: Konrad Windszus
>
> With the addition of FELIX-5207 and the SSL Filter (described in 
> http://felix.apache.org/documentation/subprojects/apache-felix-http-service.html#ssl-filter-configuration-properties)
>  it seems that there are two different mechanisms in place to actually 
> achieve the same. Please clarify in the documentation how these two relate 
> and which one to choose for which use case. Even the SSL filter allows to 
> configure the headers since https://issues.apache.org/jira/browse/FELIX-4330.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to