Hi,
I'm running Netware 6.5 Service Pack 1 and Apache 2.0.50, fresh out of the box. At the end of httpd.conf I added the following:
Alias /files "sys:/files"
<Directory "sys:/files">
Order deny,allow
Allow from all
Options Indexes
</Directory>
In sys:/files, I have a file called containing a non-7-bit-ASCII character: mér.txt (m, e with an acute accent, r). The problem is that any HTTP request for that file returns a 404 error (I didn't type the file, I clicked on it from the directory listing in a browser - Opera 7.53 an IE 6.0).
The directory listing received by the browser contains this:
<a href="m%83r/">mér/</a>
Naturally, the browser requests m%83r, but it receives a 404.
Now I did the same thing with Apache 1.3.31: fresh installation, added the "files" to httpd.conf, and, lo and behold, the file IS accesible.
To eliminate a possible misconfiguration in the 2.0.50 httpd.conf, I overwrote it with the httpd.conf from 1.3.31, did the necessary changes for Apache 2 not to complain, but, as expected, the non-standard-ASCII file was still not accessible.
So I gather it's either an httpd.conf option which is by default enabled in Apache 1 but disabled in Apache 2, or that Apache 2.0.50 has some bugs/problems with handling such international characters on Novell Netware 6.5 SP1.
This problem is starting to drive me nuts. Could anyone help?
Many thanks,
Dan
--
Do You Yahoo?! NO, THANK YOU!
Get rid of ads and banners in e-mail with Proxmail!
I'm running Netware 6.5 Service Pack 1 and Apache 2.0.50, fresh out of the box. At the end of httpd.conf I added the following:
Alias /files "sys:/files"
<Directory "sys:/files">
Order deny,allow
Allow from all
Options Indexes
</Directory>
In sys:/files, I have a file called containing a non-7-bit-ASCII character: mér.txt (m, e with an acute accent, r). The problem is that any HTTP request for that file returns a 404 error (I didn't type the file, I clicked on it from the directory listing in a browser - Opera 7.53 an IE 6.0).
The directory listing received by the browser contains this:
<a href="m%83r/">mér/</a>
Naturally, the browser requests m%83r, but it receives a 404.
Now I did the same thing with Apache 1.3.31: fresh installation, added the "files" to httpd.conf, and, lo and behold, the file IS accesible.
To eliminate a possible misconfiguration in the 2.0.50 httpd.conf, I overwrote it with the httpd.conf from 1.3.31, did the necessary changes for Apache 2 not to complain, but, as expected, the non-standard-ASCII file was still not accessible.
So I gather it's either an httpd.conf option which is by default enabled in Apache 1 but disabled in Apache 2, or that Apache 2.0.50 has some bugs/problems with handling such international characters on Novell Netware 6.5 SP1.
This problem is starting to drive me nuts. Could anyone help?
Many thanks,
Dan
--
Do You Yahoo?! NO, THANK YOU!
Get rid of ads and banners in e-mail with Proxmail!