Hi Apache folks,

When I enter http://x.x.x.x/docs/$B$"$$$&$($*(B.pdf (x.x.x.x
a japanese system) from my firefox browser, I could see that my browser
translates the URI resource portion to UTF-8 encoded formated
(%E3%81%82%E3%81%84%E3%81%86%E3%81%88%E3%81%8A.pdf) which is as expected.

But although the file is avialable on the specified path, my apache server
fails with 404 error. In further analysing the problem, I could see that the
problem could be because apache internally translates/maps URI *$B$"$$$&$($*(B.pdf*
to *49/%82%a0%82%a2%82%a4%82%a6%82%a8.pdf *, which is in shift_JIS format
instead & thus failing when the incoming request is UTF-8 encoded resource
path. And also, when I enter http://x.x.x.x/docs/*
49/%82%a0%82%a2%82%a4%82%a6%82%a8.pdf * from my browser I could see that the
document is getting displayed as expected.

I had tried AddDefaultCharset, AddType, AddCharset derivatives; but nothing
worked as expected.

Could you please let me know if there is any means (httpd.conf configuration
option) with which apache could handle the UTF-8 encoded resource path as
well.

Thanks and regards,
Sathya


Hi Apache folks,
 
When I enter http://x.x.x.x/docs/$B$"$$$&$($*(B.pdf  (x.x.x.x a japanese system) from my firefox browser, I could see that my browser translates the URI resource portion to UTF-8 encoded formated (%E3%81%82%E3%81%84%E3%81%86%E3%81%88%E3%81%8A.pdf) which is as expected.

 
But although the file is avialable on the specified path, my apache server fails with 404 error. In further analysing the problem, I could see that the problem could be because apache internally translates/maps URI $B$"$$$&$($*(B.pdf  to 49/%82%a0%82%a2%82%a4%82%a6%82%a8.pdf , which is in shift_JIS format instead & thus failing when the incoming request is UTF-8 encoded resource path. And also, when I enter http://x.x.x.x/docs/49/%82%a0%82%a2%82%a4%82%a6%82%a8.pdf  from my browser I could see that the document is getting displayed as expecte
d.

 
I had tried AddDefaultCharset, AddType, AddCharset derivatives; but nothing worked as expected.
 
Could you please let me know if there is any means (httpd.conf configuration option) with which apache could handle the UTF-8 encoded resource path as well.
 
Thanks and regards,Sathya

Currently Viewing : This Article	sathya sai		2009-01-07 11:18:01
Click Here	sathya sai 2009-01-08 04:30:55
Click Here	Eric Covener 2009-01-08 04:38:02
Click Here	sathya sai 2009-01-08 04:51:44
Click Here	Eric Covener 2009-01-08 12:04:29
Click Here	sathya sai 2009-01-09 18:33:34
Click Here	Bob Ionescu 2009-01-09 20:09:16

---