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

Felix Meschberger resolved FELIX-3295.
--------------------------------------

    Resolution: Fixed

Implemented support for this configuration property in Rev. 1227558 and updated 
the documentation of configuration properties on the site 
(https://cwiki.apache.org/confluence/display/FELIX/Apache+Felix+HTTP+Service)
                
> Allow configuration of Http Service context path
> ------------------------------------------------
>
>                 Key: FELIX-3295
>                 URL: https://issues.apache.org/jira/browse/FELIX-3295
>             Project: Felix
>          Issue Type: New Feature
>          Components: HTTP Service
>    Affects Versions: http-2.2.0
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: http-2.2.2
>
>
> We have a need that we want our Http Service based application to not always 
> run on the root context path.
> The use case is that we have a single reverse proxy in front of multiple 
> instances of our application and we forward to the different instances based 
> on the URL path. For simplicity we don't want to rewrite the paths and thus 
> the easiest thing is to run the instances with different context paths.
> The proposed solution is simple: We add a new configuration property 
> "org.apache.felix.http.context_path" (named after the request property 
> "javax.servlet.include.context_path" indicating the context path on 
> RequestDispatcher.include). This defaults to "/" and may be any path with a 
> leading slash (enforced if missing) and no trailing slash (removed if 
> provided).
> The value of this property (or the default) is then used to create the 
> Context for Jetty.
> This is also referred to by a post on the users list [1].
> [1] http://markmail.org/message/gwnct4675htaf7jc

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to