httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Boyle Owen" <>
Subject RE: [users@httpd] headername
Date Tue, 17 Sep 2002 10:37:55 GMT
I think the main point is that HeaderName is only invoked when there is a request which leads
to a directory listing. In this event, apache has a valid directory to access. The filename
argument to HeaderName is therefore taken relative to that directory. I guess that if you
tried an absolute path (e.g. /home/web/header.html) and you were trying to list mydir with
docroot /home/web/html, then apache would end up looking for /home/web/html/mydir//home/web/header.html
- which obviously wouldn't exist and you'd get a 404.

>-----Original Message-----
>From: Rich Bowen []
>Sent: Dienstag, 17. September 2002 12:29
>Subject: RE: [users@httpd] headername
>On Tue, 17 Sep 2002, Boyle Owen wrote:
>> Apparently not. In the docs (hint, hint..) it says:
>> "Filename is treated as a URI path relative to the one used 
>to access the directory being indexed".
>> Which implies you cannot use an absolute pathname. One 
>workaround might be to make a symbolic link in every indexed 
>directory to the common file (make sure you have "Options 
>It is still early here, and I am pre-caffeine, but my recollection is
>that absolute paths are considered to be relative to the ServerRoot,
>whereas relative paths are relative to the current directory. I should
>probably verify this ...
>Rich Bowen -
>Author - Apache Administrator's Guide
>The official User-To-User support forum of the Apache HTTP 
>Server Project.
>See <URL:> for more info.
>To unsubscribe, e-mail:
>   "   from the digest:
>For additional commands, e-mail:

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message