well i got one promising reply, which i admit i haven't had time to check out:
>>>>> w trillich wrote: > speaking of autoindex issues-- i can't get apache to > display the HEADER or README files (above and > below the tabular file listing), and when i posted > my most recent question, someone else piped up and > said they've got the same snag. > > is there a configuration that turns off the inclusion > of plain text header/footer? it seems to be site-wide > for us... Add something like this for the <Directory> sections you want to have display the header and footer: <Files ~ "(README|HEADER)$"> ForceType text/plain </Files> Apparantly the DefaultType setting isn't being honored for this case. Sorry if this was already answered, but I didn't see it come up. -- ( 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 ) <<<<< thanks, mike! BUT-- even if that works, the apache dox say that you can have a HEADER.html or README.html file, which also doesn't work on our 1.3.9 server... so, what we'd already done, instead, was to create our own /cgi-bin/index.pl script to generate listings that would keep hackers guessing as to what type of server we're running. (kinda a roll-our-own deception toolbox, as it were; you can spot an apache index listing at fifty paces.) we also added filtering capabilities, where the script looks for "./.index" and checks for ^\s*(show|hide)\s*=\s*(.*) to know what to include/exclude in the grep//,readdir(). our next step is to make it an Apache::Registry handler instead of a resource-hogging cgi script. (once we get these darn client demands our of our way...) -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- Their is five errers in this sentance.
