Re: Differences between different Apaches in file requests

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks you for trying to revive this case in Apache bugzilla.

2008/9/25 André Warnier <aw@xxxxxxxxxx>
Hi.

I searched the Apache bugzilla database and came up with a similar issue posted a while ago (bug # 18805).  I posted an additional comment there, describing the issue as we see it, in the hope that it will revive the case.

I will also try to start another thread here dedicated to such URL character issues, hoping to provoke some serious debate.

In any case, thanks for bringing this problem up.  I have been using Apache for a very long time, and I am also not an native English-speaker.  I can't imagine that I have not encountered the same issue before, so I can only imagine that this logic is relatively new in Apache under Windows.

André


André Warnier wrote:
#V[Á]lentín wrote:
I still think that there is an Apache 2.x + Windows related problem...

I definitely agree.
The browser should not have to "guess" the character encoding that the server uses in its filesystem.
And 403 is the wrong response, even if the filename encoding does not match.


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. <wrowe@xxxxxxxxxxxxx>

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: users-unsubscribe@xxxxxxxxxxxxxxxx
 "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx





---------------------------------------------------------------------
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: users-unsubscribe@xxxxxxxxxxxxxxxx
 "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx



---------------------------------------------------------------------
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: users-unsubscribe@xxxxxxxxxxxxxxxx
 "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx



[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux