| I see couple of issues in delivering fcgid.conf and security.conf .
| Since these are now delivered as separate configuration files and will
| be read only after reading the entire httpd.conf, customers who want to
| customize the features of this module will now have no reliable way of
| configuring it within multiple virtual servers.
The config files can always be customized or even removed altogether.
They are intended more as a simple starting point that works out of the box
rather than a one-size-fits-all delivery. The user is welcome to modify it
in any way he wants. (This is the approach taken by most other components.
For e.g. Squid can be configured as a reverse proxy, but the
common use is to configure it as a forward proxy, hence we supply the
configuration that works as a forward proxy as a starting point.
| consider an example - if I would like to configure 10 multiple virtual
| servers within 'httpd.conf' and configure some fastcgi configuration in
| few of them and security rules in the other. Since, fastcgi and security
| features would not have been loaded customer would have hard time
| understanding / trouble shooting the problem.
| Historically, some modules will have to be loaded ahead of the other for
| it to work successfully. I am not sure, if these modules have such
| restriction. For example, will there be any issue if a 3rd party module
| is loaded ahead of mod_security.so because of this dispersed approach .
neigher am I. But I suppose that for those modules that have this
restriction, it would be be better to supply a module.sample rather than a
module.conf with a warning on the top of the conf file advising the user
of the loading order.
rahul
--
1. e4 _
