The following reply was made to PR general/2724; it has been noted by GNATS.
From: [EMAIL PROTECTED] To: Marc Slemko <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: Re: general/2724: a permanent redirect (status code 301) to a no Date: Wed, 29 Jul 1998 15:22:23 +0001 Thanks very much for your quick answer. On 28 Jul 98 at 23:22, Marc Slemko wrote: > Erm... what does this have to do with the redirect? Nothing. My mistake...I just noticed the problem in connection with a redirect, and misinterpreted the cause. But I think I have now clarifed the issue. > Any access to /staff/stats.html gives the same error regardless of the > redirect. Somehow, you have your server configured to deny access to the > file. This can be configured even though the file doesn't exist. I respectfully beg to disagree. I don't think it is a problem/issue with server configuration, but with the apache source code. Here are the results of your tests. From access_log: 207-178-54-226.go2net.com - - [29/Jul/1998:08:23:00 +0200] "GET /staff/stats.htm HTTP/1.0" 404 209 207-178-54-226.go2net.com - - [29/Jul/1998:08:23:06 +0200] "GET /staff/stats.html HTTP/1.0" 403 214 207-178-54-226.go2net.com - - [29/Jul/1998:10:09:28 +0200] "GET /staff/stats.html HTTP/1.0" 403 214 From error_log: [Wed Jul 29 08:23:00 1998] [error] File does not exist: /home/httpd/html/staff/stats.htm for 207-178-54-226.go2net.com [Wed Jul 29 08:23:06 1998] [error] client 207-178-54-226.go2net.com denied by server configuration: /staff/stats.html [Wed Jul 29 10:09:28 1998] [error] client 207-178-54-226.go2net.com denied by server configuration: /staff/stats.html But why is it that your first attempt: /staff/stats.htm returns a "not found" (status 404) while your second (and third) attempt /staff/stats.html returns a "forbidden" (status 403)? I have checked over my .conf files, and I have not made any configurations for the /staff directory (or specific locations that involve /staff/stats.html). But your test has helped me to localize what I believe to be the main issue. It arises because these files sit on a Novell server, which the Linux server can access. The Linux Novell client can only read 8.3 filenames. Usually Apache will reply that the File name is too long. And it does so when I use a lynx browser...as shown below.. 1. [Wed Jul 29 13:38:40 1998] [error] File does not exist: /home/httpd/html/staff/stats.htm for pc126.psy.aau.dk 2. [Wed Jul 29 13:38:57 1998] [error] (36)File name too long: client pc126.psy.aau.dk denied by server configuration: /staff/stats.html 3. [Wed Jul 29 13:39:20 1998] [error] (36)File name too long: client pc126.psy.aau.dk denied by server configuration: /staff/a.html The first case is as it should be...the file does not exist. The next two show that the .html is the problem. (For some reason, this "File name too long" does NOT show up when Netscape is used as a browser. Here is another example from another directory....just to show that /staff is not a special case, because of configuration. 1. [Wed Jul 29 13:40:46 1998] [error] File does not exist: /home/httpd/html/institut/a.htm for pc126.psy.aau.dk 2. [Wed Jul 29 13:40:54 1998] [error] (36)File name too long: client pc126.psy.aau.dk denied by server configuration: /institut/a.html I can see that '(36)File name too long' comes from the ap_log_error() in src/main/http_log.c and reflects the operating system (in this case of Linux, the values come from /usr/include/asm/errno.h), and not the Apache code. The "denied by server configuration" is my own modification to the get_path_info() in /src/main/http_request.c but this leaves me still with two questions: 1. Why does the lynx browser result in a file name too long error but the Netscape browser does not -- for the same URL? 2. For both browsers, when they try to read a "file name too long" file, the response is "HTTP_FORBIDDEN" ... shouldn't it be "HTTP_NOT_FOUND"? Thanks for your consideration.
