[
https://issues.apache.org/jira/browse/FELIX-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531023
]
Rob Walker commented on FELIX-379:
----------------------------------
Felix
Just one request would be to check that this doesn't disturb session
contexts/cookie handling.
It's a long time back I looked at this code, but I seem to remember some wiring
was needed between the contexts we hold in the HttpService and those Jetty uses
for managing session context. Would guess this is all still ok, but would be
good to verify it.
Sorry for being bit late to the party on this one...
-- Rob
> 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.
