Path mapping will match on a partial substring

Fixed in SVN r670

tim,

thanks for this fix, but a small problem...the isPathWildcardMatch can
create upto 3 new strings when it should not need to create any.

As a often called method it would be good to optimize this (but without
adding the bugs that I obviously had

I would use a region match and then check the character after
the region to see if it is / ; # ? etc.

assign the bug to me if you want me to do this.

cheers

while pondering if # and ? support was needed, i ended up fixing this.
I don't think # and ? are needed, but added support for them anyway in case paths from other sources are passed in....

But now I am thinking that is wrong.... because this is a decoded path and
/foo%3F should not match /foo/*

I will back that bit out....

OK - this is still not right

/foo%3B should not match /foo/*

so the problem is not in pathMap - the ;arg should not be offerred to
the PathMap match UNLESS it was encoded in the original URL.

obviously it is too late for me to be coding ... so i will leave this for now
and think about it....

OK - the fix was to remove all support for ; and ? from PathMap. In Jetty6, these are stripped out long before pathmap is called and any special characters that are there were encoded and are part of the path
and non special.

So PathMap got a little cleaner as a result of this.

Closing issue.
Appears to have been satisfactorily fixed in 6.0.0rc1