I still think that there is an Apache 2.x + Windows related problem...
because, as I said before, with Apache 1.3 + Windows I had no problems:

With Apache 1.3, if I try to get a file called /í.JPG I could do it asking
> for /%ED.JPG to the server, and this works perfectly.
>

and *the file is exactly the same*.

2008/9/24 William A. Rowe, Jr. <[EMAIL PROTECTED]>

> André Warnier wrote:
> >
> > I created a file called "valentín.jpg" in my document root and tried to
> > access it with Firefox, and I get a 403 forbidden response.
>
> All filenames on unix are whatever arbitrary characters happen to relate
> to those names.  So for files named in utf-8, they must be %escaped utf-8
> characters, those in iso-8859-1 or -15 must similarly be %escaped.  Of
> course this means an autoindex list (or even 'ls' command) is a mess with
> filenames of different encodings in the same directory.
>
> On windows, any file is accessible with utf-8 characters, since Windows
> filenames are actually unicode filenames.  There's no way to map these
> all, except for utf-8.
>
> So the actual href/src link targets must be spelled out in %escaped utf-8
> and you'll have no issues.  My personal preference for figuring out the
> encoding is just to look at the autoindex output from whatever directory
> (unix or windows) that I'm looking at, and cutting and pasting those links.
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: [EMAIL PROTECTED]
>   "   from the digest: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to