Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
As correctly described on this merge request: https://github.com/php/php-src/pull/1197/files
PHP in FPM mode do not handle properly balancer/FastCGI requests coming from an HTTPd Apache 2.4 using the SetHandler directive.
Version-Release number of selected component (if applicable):
PHP-FPM 5.4.16 - Apache 2.4
How reproducible:
Always
Steps to Reproduce:
1.Configure a vhost with mod_vhost_alias.
2.Set a FileMatch directive catching php extension.
3.Set a SetHandler directive on the FileMatch section which delegate to a balanced proxy setup.
Actual results:
HTTP Result: 404 - File Not Found
Expected results:
HTTP Result: 200 - OK
Additional info:
If you take a look at the received packet on PHP-FPM, you'll clearly see that the SCRIPT_FILENAME variable contain bad informations.
Here is the sanitized content of the packet:
SERVER_NAME=polygon.polygon.lan
SERVER_ADDR=192.168.0.100
SERVER_PORT=443
REMOTE_ADDR=192.168.0.10
DOCUMENT_ROOT=/mnt/nfs/customers/polygon
REQUEST_SCHEME=https
CONTEXT_PREFIX
CONTEXT_DOCUMENT_ROOT=/mnt/nfs/customers/polygon
SERVER_ADMIN=exploit
SCRIPT_FILENAME=proxy:balancer://compute//mnt/nfs/customers/polygon/index.php
REMOTE_PORT=56984
GATEWAY_INTERFACE=CGI/1.1
SERVER_PROTOCOL=HTTP/1.1
REQUEST_METHOD=GET
QUERY_STRING
REQUEST_URI=/index.php
SCRIPT_NAME=/index.php
As you can see it, the SCRIPT_FILENAME variable should rather have been filed without the proxy:balancer://compute/ information coming from Apache.
Hi guys, any idea, when this fix will made its way to the upstream repository?
It kinda became quite important to have this feature for us to operate safely our PHP Base application.
(In reply to gael THEROND from comment #8)
> Hi guys, any idea, when this fix will made its way to the upstream
> repository?
> It kinda became quite important to have this feature for us to operate
> safely our PHP Base application.
Hi Gael,
have you meant, when this fix will be in RHEL repository? It is already in upstream.
We are currently working on the patch inclusion to RHEL, but we are not able to reproduce this bug. Would you mind to share with us more detailed reproducer? The best would be to attach your httpd configuration.
Thanks
Hi Luboš!
I’m glad to hear some news from RH :D
Yes, when I said upstream I mean available in RH repositories.
Please find attached a redacted version of my HTTPd folder containing only relevant configuration files.
For information, Rémi COLLET, an active member of the #fedora IRC Chan do have the exact same problem.
I talked with him previously and he is the one who suggested me to fill for a bugzilla report.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHEA-2016-2534.html