www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael McLagan <Michael.McLa...@Linux.ORG>
Subject mod_mime/2603: silent failure if mime.types is not found
Date Mon, 13 Jul 1998 10:20:12 GMT

>Number:         2603
>Category:       mod_mime
>Synopsis:       silent failure if mime.types is not found
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Jul 13 03:30:00 PDT 1998
>Originator:     Michael.McLagan@Linux.ORG
>Release:        1.3
Redhat 4.2, etc...
Using a set of configs without the "TypesConfig" pointing
at "conf/mime.types" explicitly, including mod_mime.so.
Start the server, the "Configuring Apache to use suexec 
wrapper" appears, and the server exits.  No message is 
placed on the console or in the error file.  :(

To make matters worse, if your ServerRoot is /etc/httpd and
there is a mime.types in /etc, the server starts up and runs
without comment either.

I wasted 12 hours finding out that it was mod_mime that was
causing the server to quit without explanation, and then a couple
more figuring out why it worked on one system and not the other 
(both systems were identical except for mailcap-1.0-3 vs mailcap-1.0-7)
See full description
Hows about a meaningful error message in mod_mime.c?
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]

View raw message