Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Bug in PathMap
Opened up bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=416787

This code has been like this since the implementation of Servlet Spec 2.2 (I have no history earlier than that).
Attached a patch to the bug for our spec leads to validate.

--
Joakim Erdfelt <joakim@xxxxxxxxxxx>
Expert advice, services and support from from the Jetty & CometD experts


On Sat, Sep 7, 2013 at 4:49 PM, Joakim Erdfelt <joakim@xxxxxxxxxxx> wrote:
That is a bug, and should be fixed.

However, Servlet Spec 3.1 pretty much banned "" as a path spec (stating it as a mistake of past specs) and now enforces the use of "/".
If you haven't updated your code yet to use "/", you should stick with Jetty 7/8, as Jetty 9 is going to be Servlet Spec 3.1 moving forward.

--
Joakim Erdfelt <joakim@xxxxxxxxxxx>
Expert advice, services and support from from the Jetty & CometD experts


On Sat, Sep 7, 2013 at 12:38 PM, Nils Kilden-Pedersen <nils@xxxxxxxxxxxxxxxxxxx> wrote:

I think.

Got hit with a StringIndexOutOfBounds something.

Tracked it to line 404 (yeah, really) in PathMap:

char c = pathSpec.charAt(0);

Since Servlet spec 3.0, empty strings "" matches on the context root. I had a filter defined with urlPatterns={""}.

I can‘t quite figure out the validity of matching filters to context root, since I’ve seen similar reports from WebSphere and Glassfish, but regardless, the error message should be better then.

Nils


_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-users



Back to the top