ReadmeName and HeaderName in Apache

[Amir Ish-Hurwitz]

Hi,

Both ReadmeName and HeaderName somehow don't work in my Apache. Nothing
is appended to any directory listing while README and HEADER exist in the
relevant directory and are readable to all users. I have Apache 1.3.9,
Apache-SSL 1.3.9 (both Debian packages) and Apache 1.3.12 (compiled
myself). My Debian version is 2.2 and my kernel is 2.2.16. It's not really
important, but it sure is irritating. As far as I'm concerned my Apache
configuration is okay: it says

ReadmeName README
HeaderName HEADER

in srm.conf (in 1.3.9), and
in httpd.conf (in 1.3.12)

Both directives are used only once in my (general) server config, not in
any virtual host, directory or .htaccess context. The files README and
HEADER have the right permissions and UID/GID, since I can view the
content via the browser when I enter the URI (e.g.
http://www.mysite/somedir/README) manually. The required module for these
directives (autoindex_module) is loaded -- of course, otherwise the
apachectl wouldn't start apache in the first place, due to a broken
configuration.

I do know Apache has changed somewhat regarding the handling of the
ReadmeName and HeaderName directives after version 1.3.6, but I don't
want to downgrade to 1.3.6 to try it out... although I could try it on my
old 486 box, which I have to seek somewhere in the "well-organized"
storage room, though :)

Anyways, it really puzzles me.

Regards,
Amir

--
Unsubscribe? mail -s unsubscribe debian-us...@lists.debian.org < /dev/null

[Mike Brownlow]

Amir Ish-Hurwitz wrote:
> Hi,
>
> Both ReadmeName and HeaderName somehow don't work in my Apache. Nothing
> is appended to any directory listing while README and HEADER exist in the
> relevant directory and are readable to all users. I have Apache 1.3.9,
> Apache-SSL 1.3.9 (both Debian packages) and Apache 1.3.12 (compiled
> myself). My Debian version is 2.2 and my kernel is 2.2.16. It's not really
> important, but it sure is irritating. As far as I'm concerned my Apache
> configuration is okay: it says
>
> ReadmeName README
> HeaderName HEADER

<snip>

Hi Amir,
Try forcing the type of the README and HEADER files for the
directory sections you want. E.g.:

<Directory /some/dir>
Options Indexes
AllowOvrride None

<Files ~ "(README|HEADER)$">
ForceType text/plain
</Files>

order allow,deny
allow from all
</Directory>

--
( Mike Brownlow | http://wsmake.org/~mike/ | http://wsmake.org/ )
( "A scorner seeketh wisdom, and findeth it not: but knowledge )
( is easy unto him that understandeth." Proverbs 14:6 )

[Mike Brownlow]

Amir Ish-Hurwitz wrote:
> Hi Mike,
>
> Thanks, it works fine! Also as a general config, not just for a specific
> directory! But how come? Shouldn't it have worked without forcing the
> type? I'll look into it...
>
> Amir

Yeah, it used to work ok. I think some function is not setting the
content_type attribute of request_rec's correctly when unknown types
are found but DefaultType is specified. I think it is setting
content_type to NULL whereever that is. The code says in a similar
problem area:

modules/standard/mod_expires.c:430
* I still don't know *why* r->content_type would ever be NULL, this
* is possibly a result of fixups being called in many different
* places. Fixups is probably the wrong place to be doing all this
* work... Bah.