Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 65268 invoked by uid 500); 24 Jun 2001 21:57:22 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: tomcat-dev@jakarta.apache.org Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 65259 invoked from network); 24 Jun 2001 21:57:22 -0000 Date: Sun, 24 Jun 2001 08:00:16 -0700 (PDT) From: cmanolache@yahoo.com X-Sender: costin@d-ucup02-251-93.Eng.Sun.COM To: tomcat-dev@jakarta.apache.org Subject: Re: URL Decoding for %XX%XX%XX In-Reply-To: <20010625065534.A5569@voyager2.oop-reserch.co.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: localhost.apache.org 1.6.2 0/1000/N On Mon, 25 Jun 2001, Jun Inamori wrote: > IE (at least IE 5.5 on Windows95) encodes the request URL by the way of: > one Japanese character --> %XX%XX%XX > And this results in the corrupted URL String. > I'm not sure, but I remenber that Costin pointed this is the bad > behavior of IE. No, that's correct behavior. What's wrong is in the javascript method encode() where unicode chars are encoded as %XXXX. The above URL should work in tomcat33 ( M4 and after ), assuming the encoding is passed ( either you are in a session, and use the session encoding, or an hipotetical browser that sends the encoding - don't know any, or you override the default encoding for the webapp ). Costin