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 "http://localhost:8080/æøå.gif"; I > get an error 404 along with a description: "description The requested > resource (/%C3%A6%C3%B8%C3%A5.gif) is not available." This should be fine, > as Tomcat converts it to UTF-8. Directory listings worked for UTF-8 files out of the box for me although I got a 503 rather than a 404 trying to access the files. Once I set URIEncoding="UTF-8" in the connector, I could access the files without any problems. I haven't tested 5.0.x. With URIEncoding="UTF-8" everything worked in both Windows and Linux. > If I put the two files into a separate directory, eg. "test" and access the > directory like "http://localhost:8080/test";, I get a directory listing. OK. This is the first thing to fix. get this working and then worry about accessing the file. > I am running Apache 5.0.x and 5.5.x on Suse Linux 10.x. I can verify that > the errors should have nothing to do with file permissions or browser > errors. I can open the file " æøå.gif" with a standard image viewer. Which versions? Looking at the svn history for the default servlet it looks like the fix for 40901 had some positive unintended consequences. This fix is in 5.5.21 onwards. > I have tried setting 'URIEncoding="UTF-8"' in the port 8080 connector, but > without success. You'll need this once directory listings are working. > What do I do? Hopefully an upgrade to 5.5.21 will fix this. 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]
![http://localhost:8080/æøå.gif"](http://localhost:8080/æøå.gif"){kind=link}