Filenames with unicode characters

Hello Everyone,

I have a problem with ISS and unicode files.
I want to download a file with unicode char in them but ISS doesn't give the
file back.

When I look in the logs I’m getting:
2007-08-01 07:38:40 127.0.0.1 - W3SVC1 PC-EDWARD 127.0.0.1 80 GET
/ManagementConsole/DOWNLOAD/tempFinal/kujw4728KU___1_8_2007_ __8_47_3/XML/TEST_UNICODEΐΩΪάΛΜήΗΆΒΤыэцф.txt_ 1.xml
- 404 2 4203 719 0 HTTP/1.1 localhost
Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+.NET+CLR+ 1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30) - -

You can see thet the server is responding with 404 but the file
"TEST_UNICODEΐΩΪάΛΜήΗΆΒΤыэцф.txt_1.xml" exist on the server.
When I remove the unicode chars I can download the file.

I tested it on a windows 2003 machine and on windows XP and both have the
problem.

Is there a setting in IIS to support unicode in the file names?

Thanks

Re: Filenames with unicode characters

On Aug 1, 12:48 am, rvangeldrop
wrote:
> Hello Everyone,
>
> I have a problem with ISS and unicode files.
> I want to download a file with unicode char in them but ISS doesn't give =
the
> file back.
>
> When I look in the logs Iâ€=99m getting:
> 2007-08-01 07:38:40 127.0.0.1 - W3SVC1 PC-EDWARD 127.0.0.1 80 GET
> /ManagementConsole/DOWNLOAD/tempFinal/kujw4728KU___1_8_2007_ __8_47_3/XML/=
TE­ST_UNICODEΐΩΪάΛΜή ΗΆ=CE=
’ΤыэцÑ=84.txt_1.xml
> - 404 2 4203 719 0 HTTP/1.1 localhost
> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.1;+.NET+CLR+ 1.1.4322;+.NE=
T+­CLR+2.0.50727;+.NET+CLR+3.0.04506.30) - -
>
> You can see thet the server is responding with 404 but the file
> "TEST_UNICODEΐΩΪάΛΜή=CE=9 7ΆΒ=
Τыэцф.txt_1.xml" exist on the server.
> When I remove the unicode chars I can download the file.
>
> I tested it on a windows 2003 machine and on windows XP and both have the
> problem.
>
> Is there a setting in IIS to support unicode in the file names?
>
> Thanks



IIS6 natively supports Unicode in resource names and the virtual URL
namespace. It is always enabled and cannot be disabled.

If you get a 404, it means that you are not sending a properly encoded
URL. You need to either use %-encoded UTF8 representation of Unicode,
or only send DBCS encoding of the Unicode characters where client and
server's codepage match.

FYI: This is not IIS-specific behavior. You need to read and
understand I18N support from public specs if you want to test/support
it.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//