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 <[email protected]> webtide.com <http://www.webtide.com/> - intalio.com/jetty Expert advice, services and support from from the Jetty & CometD experts eclipse.org/jetty - cometd.org On Sat, Sep 7, 2013 at 12:38 PM, Nils Kilden-Pedersen < [email protected]> 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 > [email protected] > https://dev.eclipse.org/mailman/listinfo/jetty-users > >
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
