Antw: RE: Bug in Tomcat 3.3.1 with getPathInfo() ?

2002-04-11 Thread Olaf Vetter
But URLEncoder.encode( myPath ) encodes ' ' to '+', not '%20'... Creating extra path info gets quite difficult now. [EMAIL PROTECTED] 10.04.2002 19:14 I think if request.getPathInfo() returns '/Hit+Run', then the path info was '/Hit+Run' or '/Hit%2BRun'. The path would have to be

Bug in Tomcat 3.3.1 with getPathInfo() ?

2002-04-10 Thread Olaf Vetter
As far as I understand, calling request.getPathInfo() should return an encoded string. With Tomcat 3.3.1, it returns the plus sign instead of encoding it to a space. (Besides, it works ok with Tomcat 3.2X) Is this a bug or intended? Thanks in advance Olaf Vetter -- To unsubscribe: mailto

RE: Bug in Tomcat 3.3.1 with getPathInfo() ?

2002-04-10 Thread Olaf Vetter
OK. But now, is there any way to distinguish between a '+' that results from encoding '%2B' and a '+' that stands for ' ' ? In other words, if request.getPathInfo() returns '/Hit+Run' , this could be '/Hit+Run' or '/Hit Run' ... Olaf [EMAIL PROTECTED] 10.04.2002 17:07 According to RFC2396,