using special chars in filenames.

[phara0h01]

I am having problems using special chars in filename (I have a 3. part application using this).

If you are using firefox, then firefox fixes the url to the second example itself. But in IE apache says that the file is missing.

the file: http://example.com/tøst.php
The apache says that is does not exist.

now, try this: http://example.com/t%F8st.php

Is there any way to make this work with apache? (Like telling apache to fix the url itself?)

[edited by: jdMorgan at 3:01 pm (utc) on Feb. 24, 2006]
[edit reason] No specifics, please. See Terms of Service. [/edit]

[phara0h01]

I just tried the link I posted, and the link works, but if I copy / paste the link into the adressbar of IE it does not work. So try copy paste this code into IE: example.com/tøst.php (this forum uses some kind of redirect script for urls)

[edited by: jdMorgan at 3:02 pm (utc) on Feb. 24, 2006]
[edit reason] Obscured specifics. [/edit]

[jdMorgan]

phara0h01,

Welcome to WebmasterWorld!

Please take a moment to review the WebmasterWorld Terms of Service [webmasterworld.com] and our forum charter [webmasterworld.com].

The character-set allowed in URIs is quite limited. Characters having values outside the range of hexadecimal 00-7f are not allowed at all, and many characters within that range are restricted as well. Some characters are allowed in the query string, but not in the URL. Perhaps the best source for comprehensive information is RFC 2396 - Uniform Resource Identifiers (URI): Generic Syntax [faqs.org].

The basic answer to your question is most likely this: Any non-ASCII characters must be converted to their hex-encoded equivalent before being used in a link. This conversion is done automatically by some browsers in some cases (keyboard entry), but perhaps not in others (paste operation).

A review of RFC2396, particularly Section 2, will help to clarify the issue.

You may want to try setting up some experimental rewrites or redirects, testing them, and examining your raw server error log file to see exactly what the problem is. This will indicate the best way to fix it. Once you've identified the problem more specifically, we can probably be more helpful.

Jim