[
https://issues.apache.org/jira/browse/FELIX-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15013361#comment-15013361
]
Rob Walker edited comment on FELIX-5109 at 11/19/15 11:19 AM:
--------------------------------------------------------------
Just want to clarify this one - as down the year's it been a bit of an awkward
area, not helped by the relevant part of the HttpService spec being a little
tricky to decipher.
Are we saying this is a an actual bug i.e. the Felix Http bundle is not
functioning according to the OSGi HttpService.
Or are we saying this is actually an underlying discrepancy between the Servlet
spec and the OSGi HttpService spec.
If it's the latter case then, IMO, Felix needs to follow the OSGi spec - even
if it is at odds somewhat with the Servlet spec.
I believe (and stand to be corrected) that the OSGi HttpService alias is
consider a root path i.e. if I mount a service at /foo then I expect to see
requests for all sub-paths of /foo as well. I'm pretty sure that's how our
application is coded, and we've tried to only use the HttpService according to
the standard vanilla OSGi form.
Happy to be corrected if I've misunderstood this.
was (Author: walkerr):
Just want to clarify this one - as down the year's it been a bit of an awkward
area, not helped by the relevant part of the HttpService spec being a little
tricky to decipher.
Are we saying this is a an actual bug i.e. the Felix Http bundle is not
functioning according to the OSGi HttpService.
Or are we saying this is actually an underlying discrepancy between the Servlet
spec and the OSGi HttpService spec.
If it's the latter case then, IMO, Felix needs to follow the OSGi spec - even
if it is at odds somewhat with the Servlet spec.
I believe (and stand to be correct) that the OSGi HttpService alias is consider
a root path i.e. if I mount a service at /foo then I expect to see requests for
all sub-paths of /foo as well. I'm pretty sure that's how our application is
coded, and we've tried to only use the HttpService according to the standard
vanilla OSGi form.
Happy to be corrected if I've misunderstood this.
> Wrong path matching for http and http whiteboard service
> --------------------------------------------------------
>
> Key: FELIX-5109
> URL: https://issues.apache.org/jira/browse/FELIX-5109
> Project: Felix
> Issue Type: Bug
> Components: HTTP Service
> Affects Versions: http.base-3.0.0, http.base-3.0.2, http.jetty-3.1.0,
> http.jetty-3.1.2
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: http.base-3.0.4, http.jetty-3.1.4
>
>
> It seems we have some bugs in the path matching which result from different
> handling between the http service and the servlet spec.
> For the http service, an alias like "/foo" matches "/foo" and "/foo/*" -
> while for the servlet spec "/foo" only matches "/foo" - exact match.
> Right now, in both cases "/foo/*" matches.
> For the servlet spec a pattern like "/foo/*" matches "/foo/something" but
> also "/foo". Right now we don't handle the second case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
