httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 53099] New: feature request for mod_remoteip
Date Wed, 18 Apr 2012 11:48:28 GMT

             Bug #: 53099
           Summary: feature request for mod_remoteip
           Product: Apache httpd-2
           Version: 2.4.1
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mod_remoteip
    Classification: Unclassified

It would be nice if in mod_remoteip, you could specify a list of
headers and not just one.

suggestion is to allow multiple parameters to RemoteIPHeader, eg:

RemoteIPHeader X-Forwarded-For, X-Forward
RemoteIPTrustedProxy gateway.localdomain

Headers would preferably to be checked for in the provided order. 

Use case example is :

1. If there is X-Forwarded-For header use it (as the traffic is
through a forward proxy, such as squid)

2. Otherwise if there is X-Forward header use it (traffic is direct,
but via a SNAT-ing content switch)

3. Otherwise use the connection's REMOTE_ADDR as usual (traffic is direct - and
not via a SNAT-ing content switch OR a forward proxy)

In the current mod_remoteip, you can only pick one header - the
different headers in our case are created by different devices. The content
switch makes X-Forward with a single ip address and the forward proxy adds
X-Forwarded-For in the usual manner.

Both headers rewrite fine using the existing code, except i must choose to
rewrite either the content switch header OR the forward proxy header, but not

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message