[
https://issues.apache.org/jira/browse/FELIX-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531035
]
Rob Walker commented on FELIX-379:
----------------------------------
Thanks Felix.
In the absence of anything specific in Osgi HTTP service spec, it seems safest
to fall back to what people would consider "normal/covnetional HTTP server
behaviour" for session params, cookies etc.
I'd read the "share same namespace" aspect as being more to do with Paths than
session params etc. - but I'm not an expert in this area.
As per my email, my very old HTTP Test bundle that I used initially to find our
original "hole" in session param handling and fix it is still in the OBR if
needed:
http://oscar-osgi.sourceforge.net/
> Registering multiple servlets may hide some
> -------------------------------------------
>
> Key: FELIX-379
> URL: https://issues.apache.org/jira/browse/FELIX-379
> Project: Felix
> Issue Type: Bug
> Components: HTTP Service
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 1.0.0
>
> Attachments: FELIX-379.patch
>
>
> Consider registering a servlet RootServlet for "/" first and then a servlet
> SomeServlet for "/some" with different OSGi HttpContext instances in this
> order with the http.jetty HttpService. This registration works absolutely
> correct and also creates the necessary setup internally. Unfortunately, when
> Jetty now receives a request for "/some", it first calls the RootServlet
> instead of the SomeServlet as would be expected according to the HttpServlet
> Service specification.
> If the servlets are registered SomeServlet first and then RootServlet it
> works perfectly.
> I think it is related to the fact, that the http.jetty bundle registers a
> jetty context for "/" for each different OSGi HttpContext and jetty asks
> these registrations in registration order, which may not be correct according
> to the spec. Probably, there should only be one actual web app registration
> with jetty and the http.jetty bundle should multiplex between the different
> OSGi HttpContext instances and select the correct servlets.
> I am working a possible solution to this right now.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
