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 '/Hit

RE: Bug in Tomcat 3.3.1 with getPathInfo() ?

2002-04-10 Thread Larry Isaacs
age- > From: Olaf Vetter [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, April 10, 2002 11:20 AM > To: [EMAIL PROTECTED] > Subject: RE: Bug in Tomcat 3.3.1 with getPathInfo() ? > > > OK. But now, is there any way to distinguish between a '+' > that results from enc

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 RFC2

RE: Bug in Tomcat 3.3.1 with getPathInfo() ?

2002-04-10 Thread Larry Isaacs
According to RFC2396, '+' is are reserved character in the query string, but not in the path portion of a URL. There was a bug fix in Tomcat 3.3.1 to avoid translating '+' to ' ' in the parts of the URL prior to the query string. Cheers, Larry > -Original Message- > From: Olaf Vetter [m