• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 352
  • Last Modified:

Getting non-ascii chars in URLs passed correctly. Getting 404s due to "ascii-ifying" URLs

I have some files on my web server with non-ascii (in fact, non-Latin) chars in their filenames.
For example:

That is, letter r, then letter o with double acute accent, letter L, and the extension.  The double acute accent is detailed here:

It looks like this site is also unablwe to show the character correctly.  Tsk tsk.

When I make a request for the page, I always get a 404.  Looking in the logd I see that the server is seeking rol.txt, and of course not finding it.
THis is true using

In the IIS logs I see:
21:45:38 GET /rol.txt - 404 3535 819 40  ...

My Web.sitemap contains the correct URL with the accented character.

It appears that the browser is making the correct request, but that the server is not seeing the right chars, URL-encoded or not.
Please advise how to make this work.
  • 5
  • 3
1 Solution
URLs should be encoded before passing.  At the moment, not all systems support internationalised URL encoding as described here http://www.w3.org/International/O-URL-code.html

Your best bet is to sanitise filenames before they are stored on your server.

Otherwise, you may find that the international encoding described above will help.
Note that many URL encoding schemes encode URLs according to the non-internationalised standard, i.e. they only support 7-bit ASCII, or if you are lucky 8-bit.  Neither of these support Unicode directly.
dc197Author Commented:
I developed the site using VS2005 and its internal webserver.  This fully supports unicode chars, and the site works just fine, whether one uses URL-encoded requests or not.

I copied the source over to my dev machine for testing, which is running IIS5 as the webserver.  This is where the problem arose.   Is IIS5 the culprit?  Is IIS6 better?
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

See http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/23ec8be2-649a-47b7-8d75-ffd937f16fe8.mspx?mfr=true

Yes, new in IIS 6

The paragraph at the bottom of the above page reads:

Because IIS 6.0 now supports UTF-8 URLs, you can now log those URL requests to an ASCII log file. UTF-8 is a double-byte character set standard. Because ASCII is a single-byte character set standard, logging UTF-8 information to an ASCII file presents a problem. In such a case, ? is logged for the characters that cannot be converted to the codepage of the server.
dc197Author Commented:
OK it looks like IIS6 has support for unicode URLs (http://msdn.microsoft.com/msdnmag/issues/02/03/IIS6/) as well as better logging. That's good, because the site I wish to host heavily features the Hungarian language, in which o is not the same as ó, ö or ő.

dc197Author Commented:
It would appear that this site's ability to handle non-standard chars sucks, too.
Actually, they have recently opened an Experts Exchange bug on this issue, and I have been assisting!

It's a fairly standard issue.  For example the PHP language doesn't support Unicode particularly well, and it certainly can make coding harder.

Nevertheless, in my view that is no excuse and I always make sure any forms I code support Unicode fully and do not assume Latin character sets unless appropriate!
So, if you are coding for Hungarian, I recommend that you encode your pages in UTF-8, that you use HTML entities for posting/returning form values, that you always set the HTTP headers (not just those in the HTML page!) and that you TEST, TEST, TEST!

Good luck :)
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now