2010/10/13 Mark Thomas <ma...@apache.org>: > I'm not against switching from a pair to a triple for this but a) I'm > not sure many (any?) folks are using path parameters apart from for > session IDs
I will think more on it and do some testing, what of our APIs are exposing them, but just from reading RFC 3986 ch.3.3 [1] I think the representation of them as a simple HashMap<name,value> is inadequate. http://tools.ietf.org/html/rfc3986#section-3.3 > and b) I think the 404 is a more important issue. Is it possible to fix the client that sends those requests? Or apply a Valve/Filter? Though, well, I can imagine a scenario that this issue may be seen a) start Tomcat and make a bookmark that includes jsessionid in its path b) reconfigure Tomcat to use a different name for jsessionid parameter c) the bookmark no longer works. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
