There is also a bug in 3.3 ( where URI is also decoded ),
I'm working on it - should be ready this weekend.
( I'm also working on the " " bug, it has the most votes so far )
Costin
On Fri, 18 May 2001, Keith Wannamaker wrote:
> The 2.2 servlet spec errata says the uri from
> HttpServletRequest
>I just tried this and verified the orginal bug and that the
>proposed patch
>does fix the problem. I'm OK with committing to the tomcat_32 branch.
>
>DOES ANYONE ELSE OUT THERE HAVE ANYTHING THEY WANT TO TELL ME?
>
>Resin would not appear to be compliant with the specification.
> The 4/27/00
>
rrata indicates that getRequestURI() should return the encoded value.
> -Original Message-
> From: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 18, 2001 4:31 PM
> To: [EMAIL PROTECTED]
> Subject: RE: 3.2.2 mod_jk encoding issue
>
>
> Resin 1.2.5 and
nal Message-
>From: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
>Sent: Friday, May 18, 2001 11:27 PM
>To: [EMAIL PROTECTED]
>Subject: RE: 3.2.2 mod_jk encoding issue
>
>
>Seems correct to me.
>
>BTW, with the jakarta-tomcat-connector,
>this kind of native bugs fixes will app
OTECTED]
>Subject: 3.2.2 mod_jk encoding issue
>
>
>The 2.2 servlet spec errata says the uri from
>HttpServletRequest.getRequestURI() should remain encoded.
>[http://java.sun.com/products/servlet/errata_042700.html]
>
>Tomcat 3.2 standalone handles this correctly, but the
>
The 2.2 servlet spec errata says the uri from
HttpServletRequest.getRequestURI() should remain encoded.
[http://java.sun.com/products/servlet/errata_042700.html]
Tomcat 3.2 standalone handles this correctly, but the
mod_jk connector does not.
The connector uses the decoded uri from Apache (r->ur
