Re: Requesting files with non-English/international characters in their names

Chris, On 3/26/07, Christopher Schultz [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas, Thomas Peter Berntsen wrote: Without the URIEncoding=UTF-8 parameter the Danish special characters are not echoed correctly, whereas _with_ the parameter everything in the

Re: Requesting files with non-English/international characters in their names

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas, Thomas Peter Berntsen wrote: #2 [POST] should always work, assuming that you have UTF-8-ized your app. Inline SCs display correctly, form submitted SC display with errors (displayed: æøå), browser detects UTF-8. :( The JSP contains

Re: Requesting files with non-English/international characters in their names

On 3/25/07, Christopher Schultz [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas, Thomas Peter Berntsen wrote: Yes, my perception is also that ISO-8859-1 is Tomcat's default encoding. Just to be sure I edited the index.jsp of the ROOT app in which I have created

Re: Requesting files with non-English/international characters in their names

Dear Mark, Thanks for your reply. I've commented below. On 3/25/07, Mark Thomas [EMAIL PROTECTED] wrote: Thomas Peter Berntsen wrote: I have some trouble getting Tomcat to return files with non-English/international characters in their names. The good news is that this works for me. Now all

Re: Requesting files with non-English/international characters in their names

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas, Thomas Peter Berntsen wrote: Without the URIEncoding=UTF-8 parameter the Danish special characters are not echoed correctly, whereas _with_ the parameter everything in the request is echoed correctly. Okay, good. I thought you were

Re: Requesting files with non-English/international characters in their names

Thomas Peter Berntsen wrote: I have some trouble getting Tomcat to return files with non-English/international characters in their names. The good news is that this works for me. Now all we need to do is figure out why it doesn't for you ;) But when I request the other one, using

Re: Requesting files with non-English/international characters in their names

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas, Thomas Peter Berntsen wrote: Yes, my perception is also that ISO-8859-1 is Tomcat's default encoding. Just to be sure I edited the index.jsp of the ROOT app in which I have created the æøå.gif file and changed the encoding to UTF-8, but

Re: Re: Requesting files with non-English/international characters in their names

-- Forwarded message -- From: Christopher Schultz [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Date: Mon, 19 Mar 2007 12:55:30 -0400 Subject: Re: Requesting files with non-English/international characters in their names -BEGIN PGP SIGNED MESSAGE- Hash

Re: Requesting files with non-English/international characters in their names

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas, Thomas Peter Berntsen wrote: Are you serving your pages in UTF-8 encoding? Usually, the browser uses the response encoding from the previous request to submit the next request's URI. If you are using ISO-8859-1 for your web pages, then

Requesting files with non-English/international characters in their names

Hi guys, I have some trouble getting Tomcat to return files with non-English/international characters in their names. Eg. I have two files in the root app (the standard app in the ROOT folder), one named tomcat.gif and another one, which is a copy of tomcat.gif, named æøå.gif. When I request

Re: Requesting files with non-English/international characters in their names

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas, Thomas Peter Berntsen wrote: I have some trouble getting Tomcat to return files with non-English/international characters in their names. It's interesting how questions like this come in waves. I have tried setting 'URIEncoding=UTF-8' in