RE: tomcat 5.5 Unicode issues!
Hi, Well I didn’t quite understand you all the way but trying to use your example lats say I have a file named Hello%20There.html when I try to access this file I get 404. Probably because the tomcat recognize the character % as illegitimate. So is there a way to tell tomcat that special characters like % â €™ will be parsed correctly if its not Unicode issue that what can it be? Thanks in advanced
Re: tomcat 5.5 Unicode issues!
Shahar Cohen wrote: Hi, Well I didn’t quite understand you all the way but trying to use your example lats say I have a file named Hello%20There.html when I try to access this file I get 404. Probably because the tomcat recognize the character % as illegitimate. So is there a way to tell tomcat that special characters like % â €™ will be parsed correctly if its not Unicode issue that what can it be? You need to escape the % The url for that file, assuming it was located in the ROOT context would be: http://host:port/Hello%2520There.html Thanks in advanced If your file names are UTF-8 encoded then you should be using URIEncoding=UTF-8 on your connector. Mark - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: tomcat 5.5 Unicode issues!
Changing the URIEncoding=UTF-8 just worked. thanks -Original Message- From: Mark Thomas [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 20, 2008 5:29 PM To: Tomcat Users List Subject: Re: tomcat 5.5 Unicode issues! Shahar Cohen wrote: Hi, Well I didn’t quite understand you all the way but trying to use your example lats say I have a file named Hello%20There.html when I try to access this file I get 404. Probably because the tomcat recognize the character % as illegitimate. So is there a way to tell tomcat that special characters like % â €™ will be parsed correctly if its not Unicode issue that what can it be? You need to escape the % The url for that file, assuming it was located in the ROOT context would be: http://host:port/Hello%2520There.html Thanks in advanced If your file names are UTF-8 encoded then you should be using URIEncoding=UTF-8 on your connector. Mark - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: tomcat 5.5 Unicode issues!
- Original Message - From: Shahar Cohen [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Wednesday, August 20, 2008 4:15 PM Subject: RE: tomcat 5.5 Unicode issues! Hi, Well I didn’t quite understand you all the way but trying to use your example lats say I have a file named Hello%20There.html when I try to access this file I get 404. Probably because the tomcat recognize the character % as illegitimate. So is there a way to tell tomcat that special characters like % â €™ will be parsed correctly if its not Unicode issue that what can it be? Thanks in advanced Shahar, Do you see what Mark is showing you? See what has to happen now? What I'm saying is that who ever is wrting the files to disk like that in the first place has screwed up... Fix that if you can... eg /Hello There.html In the Url becomes Hello%20There.html If that is Decoded properly... and written to disk the file name will be Hello There.html But if its not decoded the file name will be.. Hello%20There.html And now to get that in a browser it becomes... Hello%2520There.html and if that is wrtten back to disk... its just a cock up .. To see what I'm saying open google Type hello there as a search... and search Then look at the URL see whats happening... that is called URL Encoding... its not unicode. . Just stop the file names from looking funny in the first place... thats what I'm saying. Who wants to type Hello%2520There.html anywhere ;) If it is a language thing as well then the UTF8 stuff is happening on top of URL Encoding... even if it is chinese... its still getting messed up... the decoding is wrong When ever you see %20 and %24 and %40 in stuff... its pretty much telling you that is not decoded. Read up on URL Encoding... its not a unicode thing... I think even if you are working with langauges... ie I'm pretty sure windows can display foreign langauges correctly and they dont have a %20 in them... is what we trying to tell you. Have fun --- HARBOR : http://www.kewlstuff.co.za/index.htm The most powerful application server on earth. The only real POJO Application Server. See it in Action : http://www.kewlstuff.co.za/cd_tut_swf/whatisejb1.htm --- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: tomcat 5.5 Unicode issues!
Thanks Mark ;) --- HARBOR : http://www.kewlstuff.co.za/index.htm The most powerful application server on earth. The only real POJO Application Server. See it in Action : http://www.kewlstuff.co.za/cd_tut_swf/whatisejb1.htm --- - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: tomcat 5.5 Unicode issues!
Shahar Cohen wrote: Changing the URIEncoding=UTF-8 just worked. Shahar, what Mark and in a more verbose way Johnny are trying to tell you, is 1) the first problem is to figure out how and why these files arrived on your system's disk with such names, and if possible correct that. They are not normal names for files, and could give you any kind of trouble in the future, such as when you will try to do a backup of your server, or list them in directories, or sort the filenames alphabetically, or access them via DAV or Samba, etc.. etc.. 2) changing the URIEncoding on your server to UTF-8 is also not something you should just do lightly and unilaterally, because you may then have problems with browsers who will *not* send request URI's as UTF-8. By default, most browsers will not, so unless you know and control who is going to access your server with what and from which pages, you are probably creating an even bigger problem for the future. André - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
