>Number:         3158
>Category:       mod_autoindex
>Synopsis:       If header or readme file exists in auto-index'd directory, 
>browsers say document empty!
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Tue Oct  6 13:50:01 PDT 1998
>Last-Modified:
>Originator:     [EMAIL PROTECTED]
>Organization:
apache
>Release:        1.3.2
>Environment:
OS:  OS/2 Warp
Using binary downloaded from Apache site (apache_1.3.2-os2.zip  from 22-sept-98)

History:  The previous version I was using was 1.2.4 and 
this problem did not exist
>Description:
History:  The previous version I was using was 1.2.4 and  this problem 
did not exist.

If I have have a file named "header", "header.html", "readme" (or 
anything else configured as the header or readme files) the client 
reports an error and the auto-index is never displayed.  Netscape 4.5pr2
reports document empty.  IE 4.0 gives more generic "can't load" error.

Using SuppressHTMLPreamble does not help.
Using plain text files does not help.
If I remove the file, everything is okay.  
What happened?  My headers USED to work in 1.2.4.

If you could e-mail a response to [EMAIL PROTECTED] and/or 
[EMAIL PROTECTED] I would greatly appreciate knowing if there really
is a bug or if I'm being an idiot and missing something obvious.  Please help.

Thanks,
Frank Domina
>How-To-Repeat:
Sorry, this server is being used inside of a firwall or I'd be glad to give you 
the URL.
>Fix:
No.
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <[EMAIL PROTECTED]> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]



Reply via email to