Bug 198206

Summary: patch to make default config file work when modules are commented out
Product: Red Hat Enterprise Linux 4 Reporter: Russell Coker <russell>
Component: httpdAssignee: Joe Orton <jorton>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-12-14 16:15:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
patch to fix this bug none

Description Russell Coker 2006-07-10 14:22:52 UTC
Created attachment 132178 [details]
patch to fix this bug

Comment 1 Russell Coker 2006-07-10 14:22:52 UTC
The attached patch puts <IfModule> directives around the config file 
directives that match every module that you might want to disable.

This means that to disable modules you merely have to comment the LoadModule 
directives, not hunt through the entire httpd.conf commenting things out all 
the way.

This is really handy when building a system to meet security standards 
documents specifying that all unnecessary software be disabled or removed.

Comment 2 Joe Orton 2006-12-14 16:15:12 UTC
Thanks for the suggestion and patch.

It is generally not desirable to over-use <IfModule in the default
configuration: if should be clear that if you disable modules then use of the
corresponding directives should cause a configuration error.  Otherwise, it
becomes a "silent failure" if people accidentally comment out a certain module,
which can be confusing and hard to diagnose.