Bug 1523536

Summary:	Backport Apache BZ#59230 mod_proxy_express uses db after close
Product:	Red Hat Enterprise Linux 7	Reporter:	Masafumi Miura <mmiura>
Component:	httpd	Assignee:	Luboš Uhliarik <luhliari>
Status:	CLOSED ERRATA	QA Contact:	Jan Houska <jhouska>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.7	CC:	bnater, jorton, luhliari
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	httpd-2.4.6-83.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-30 11:19:05 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1549494

Description Masafumi Miura 2017-12-08 09:23:53 UTC

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

Comment 7 errata-xmlrpc 2018-10-30 11:19:05 UTC

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