#V[Á]lentín wrote:
Hola Válentin.
I can't tell you what the solution is, but from the example you provide,
it looks as if Apache is accepting URLs encoded as UTF-8 (Unicode), but
not URLs encoded as iso-8859-1 (latin-1).
This is not supposed to be the standard, so there must be some setting
somewhere in the Apache configuration that triggers this.
The first place to look would be in the Apache error log, to check if
there is some additional information.
According to this :
http://en.wikipedia.org/wiki/List_of_HTTP_status_codes#4xxx_Client_Error
403 means "forbidden", while 404 is "not found".
Maybe Apache tries to decode your first URLs (where the "lowercase i
with acute" is encoded as a single byte), as a UTF-8 URL, and then finds
that this is not valid UTF-8, and then returns this code.
You also have to be quite careful under Windows between what you "see"
as file names using the Windows (disk) Explorer for instance, and how
the filenames are really encoded in the directory itself on disk, and
how Apache sees them.
I believe (but I am not sure) that in Windows directories, filenames are
stored as Unicode in UTF-16 encoding (2 bytes per character minimum,
even for a-z A-Z etc..). So even a UTF-8 encoded URL must be translated
somehow at some level, to be compared to a filename on disk.
And obviously, what you see in you Windows explorer is a "í" like in
Valentín, not 2 bytes. But internally, it is 2 bytes.
Have I added enough confusion here ?
---------------------------------------------------------------------
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]
