Bug 198200 - should have <IfModule mod_mime.c> in /etc/httpd/conf.d/php.conf
should have <IfModule mod_mime.c> in /etc/httpd/conf.d/php.conf
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: php (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Joe Orton
David Lawrence
: Reopened
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-07-10 09:48 EDT by Russell Coker
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-07-10 10:18:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
patch to fix this bug (369 bytes, patch)
2006-07-10 09:48 EDT, Russell Coker
no flags Details | Diff

  None (edit)
Description Russell Coker 2006-07-10 09:48:39 EDT
The attached patch makes the httpd work if the mod_mime.so is not loaded.
Comment 1 Russell Coker 2006-07-10 09:48:39 EDT
Created attachment 132174 [details]
patch to fix this bug
Comment 2 Joe Orton 2006-07-10 10:00:53 EDT
You should expect a configuration error if mod_mime is not loaded, since PHP
will not work otherwise.  This is desired behaviour.
Comment 3 Russell Coker 2006-07-10 10:10:21 EDT
Surely you should expect that if pre-requisite functionality is removed then 
PHP would simply be disabled.

How would you suggest handling the situation where you have multiple instances 
of Apache on one machine where one of them has PHP enabled and another 
doesn't?  Have separate conf.d directories for each instance?

I know that multiple instances of Apache is not supported (multiple copies of 
a daemon is too complex for most sys-admins to handle).  But it would be nice 
if it wasn't any more difficult than it has to be.
Comment 4 Joe Orton 2006-07-10 10:18:15 EDT
(In reply to comment #3)
> Surely you should expect that if pre-requisite functionality is removed then 
> PHP would simply be disabled.

No, silent failure is a bad thing.  If you want to complicate your configuration
with this kind of thing you can, but that doesn't mean it's necessary for the
default config.

> How would you suggest handling the situation where you have multiple instances 
> of Apache on one machine where one of them has PHP enabled and another 
> doesn't?  Have separate conf.d directories for each instance?

Yeah, or you could surround the php.conf with

<IfDefine DISABLE_PHP>

and run some httpd's with -DDISABLE_PHP on the command-line, for example.

Please take further discussion to fedora-list.

Note You need to log in before you can comment on or make changes to this bug.