RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
While using php-fpm with mod_proxy_fcgi, mod_proxy_fcgi runs into a hardcoded 30s timeout.

The variable "ProxyTimeout" isn't used, even if it's set to 600


Version-Release number of selected component (if applicable):
httpd-2.4.6-31.el7.1


How reproducible:
Set up a vhost with php-fpm and mod_proxy_fcgi and run a php script that needs regularly more than 30 seconds to run.


Actual results:

Example:

[Tue Nov 24 10:11:40.073905 2015] [proxy_fcgi:error] [pid 20800] (70007)The timeout specified has expired: [client <client>:22158] AH01075: Error dispatching request to :, referer: http://www.<host>.<tld>/typo3/mod.php?M=system_dbint&moduleToken=45b92ceb63f1fe38a01cbb410fd606f7f13fb3ff




Expected results:
ProxyTimeout is going to be considered and used if set in the configuration.


Additional info:

This bug is known and has been already fixed in upstream.
Apache Bugzilla report with patch included:
https://bz.apache.org/bugzilla/show_bug.cgi?id=54973

Apparently this bug has been already reported and also has been fixed in httpd-2.4.6-40.

I gonna wait for the new CentOS package release which should arrive soon.
So, since this bug is a duplicate of BZ#1222328 please close this report.

*** This bug has been marked as a duplicate of bug 1222328 ***