Open
Description
Describe the Bug
by default, apache::mod::fcgid
will install an essentially empty fcgid.conf
.
Expected Behavior
The configuration required by the distro should be kept intact. Specifically, AddHandler
In EL9 the distro configuration looks like this:
# This is the Apache server configuration file for providing FastCGI support
# through mod_fcgid
#
# Documentation is available at
# http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html
# Use FastCGI to process .fcg .fcgi & .fpl scripts
AddHandler fcgid-script fcg fcgi fpl
# Sane place to put sockets and shared memory file
FcgidIPCDir /run/mod_fcgid
FcgidProcessTableFile /run/mod_fcgid/fcgid_shm
The last two directives are not essential, they just move these things out of Apache's default log directory.
In Ubuntu 22.04 it looks like this:
<IfModule mod_fcgid.c>
FcgidConnectTimeout 20
<IfModule mod_mime.c>
AddHandler fcgid-script .fcgi
</IfModule>
</IfModule>
Again the timeout is not essential for operation, but AddHandler
is.
Steps to Reproduce
include apache::mod::fcgid
- see how
/etc/apache2/mods-available/fcgid.conf
(Debian flavour) loses all directives.
Environment
- Version 11.1.0
- Platform Debian, Ubuntu, EL
Additional Context
I don't think it is required to keep the configuration exactly the same, but it is unexpected that using Puppet to manage the module effectively disabled the module. I came across this while installing request-tracker5
.