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:
Backport a bug fix which was reported in the following Apache bugzilla to RHEL 7 Apache httpd:
59230 – mod_proxy_express uses db after close
https://bz.apache.org/bugzilla/show_bug.cgi?id=59230
We have a customer reported that they got 400 response infrequently during a performance test with mod_proxy_express. At the time of the issue, the following debug log message was output in error_log:
AH01141: proxy_handler no URL in proxy:/path/to/...
This is a same to the log message reported in the above bugzilla.
Version-Release number of selected component (if applicable):
The customer reported for httpd-2.4.6-45.el7_3.4 and httpd-2.4.6-67.el7 (but it looks the lastest httpd-2.4.6-67.el7_4.6.x86_64 also does not contain the fix).
How reproducible:
Infrequently
Steps to Reproduce:
Unfortunately, we do not have a reproducer for the issue.
Additional info:
The customer tried backporting the following fix and they confirmed that the 400 response disappeared with the test build in their environment.
https://svn.apache.org/viewvc?view=revision&revision=1737363
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://access.redhat.com/errata/RHBA-2018:3211