Bug 1169081

Summary:	mod_remoteip doesn't correctly set the client address reported by mod_status
Product:	Red Hat Enterprise Linux 7	Reporter:	Vadim Grinco <vgrinco>
Component:	httpd	Assignee:	Luboš Uhliarik <luhliari>
Status:	CLOSED ERRATA	QA Contact:	Martin Frodl <mfrodl>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.1	CC:	bjoern.kraus, isenfeld, jkaluza, pim
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	httpd-2.4.6-35.el7	Doc Type:	Bug Fix
Doc Text:	Cause: httpd did not set client IP address of request provided by mod_remoteip to internal shared memory. Consequence: When running httpd behind a proxy with the RemoteIPHeader and RemoteIPTrustedProxyList directives, mod_status did not show proper client IP address - it showed proxy server IP address instead. Fix: httpd has been fixed to use the IP address reported by mod_remoteip as expected. Result: mod_status is now showing proper client IP address in the mentioned case.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-19 04:36:24 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:

Description Vadim Grinco 2014-11-30 01:33:30 UTC

Description of problem:
If you have an apache 2.4 server behind a proxy, and you define the RemoteIPHeader and RemoteIPTrustedProxyList directives mod_remoteip will fail to report client ip address to mod_status. It works perfectly fine with logs (%a is correctly set), however mod_status is displaying proxy IP rather client IP


Version-Release number of selected component (if applicable):
httpd-2.4.6-18

How reproducible:
enable and configure both mod_remoteip and mod_status

Actual results:
Wrong client ip is displayed in server status page

Expected results:
See real client's IP

Comment 9 errata-xmlrpc 2015-11-19 04:36:24 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://rhn.redhat.com/errata/RHBA-2015-2194.html