Package: apache2.2-common
Version: 2.2.22-13
By default debian will have both mod_cgi and mod_cgid enabled.
When trying to disabling mod_cgi, we get:
# a2dismod cgi
Your MPM seems to be threaded. Selecting cgid instead of cgi.
This will keed mod_cgi enabled in
/etc/apache2/mods-enabled/cgi.load
Which is bad, because many debian php applications like phpldapadmin have
checks for mod_cgi, mod_cgid and not modfastcgi.
e.g from /etc/apache2/conf.d/phpldapadmin:
<IfModule mod_cgi.c>
AddType application/x-httpd-php .php
Action application/x-httpd-php /cgi-bin/php5
</IfModule>
<IfModule mod_cgid.c>
AddType application/x-httpd-php .php
Action application/x-httpd-php /cgi-bin/php5
</IfModule>
This breaks mod_fastcgi.
I understand the care of using mod_cgid instead of mod_cgi for mpm-worker.
However this care should be used only on enabling modules not disabling
them.
It is like:
ME: Apache, disable module cgid, I dont need it.
APACHE: Ok, Disable.
ME: Apache, disable module cgi, I dont need that either.
APACHE: No, cgid is more suitable for your setup. I will disable that
one instead.
ME: I really need cgi module off.
APACHE: No, you dont know what you need. I will do what _I_ want.
I don't think (but I might be wrong) that there is a scenario where you
have both mod_fastcgi and mod_cgi[d] together.
If there is these configurations should take that into consideration too
(phpmyadmin and others probably suffers the same problem).
I believe that a similar situation could happen with mpm-worker even
without fastcgi.
