Seems correct to me.
BTW, with the jakarta-tomcat-connector,
this kind of native bugs fixes will appears
outside TC 3.2/3.3/4.0 soon.
I'll correct that on mod_jk in TC 3.3 and
jakarta-tomcat-connector
To be fixed also in mod_webapp.
-
Henri Gomez ___[_]
EMAIL : [EMAIL
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 appears
outside TC 3.2/3.3/4.0 soon.
I'll
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 2.0b2 also use uri instead of unparsed_uri
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
errata
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
