[Issues] [mod_log_sql 0000010]: X-Forwarded-For header logging for proxies

issues at outoforder.cc issues at outoforder.cc
Sat Apr 16 16:41:39 EST 2005


A NOTE has been added to this issue.
======================================================================
<http://issues.outoforder.cc/view.php?id=10> 
======================================================================
Reported By:                urkle
Assigned To:                urkle
======================================================================
Project:                    mod_log_sql
Issue ID:                   10
Category:                   Feature Request
Reproducibility:            N/A
Severity:                   minor
Priority:                   normal
Status:                     assigned
Apache Version:             unspecified
======================================================================
Date Submitted:             09-05-2004 12:16 EST
Last Modified:              04-16-2005 16:41 EST
======================================================================
Summary:                    X-Forwarded-For header logging for proxies
Description: 
e-mail from Paul Chvostek

Heya.

I'm trying to get mod_log_sql running on a web server behind a proxy
(Pound, from http://apsis.ch/pound/).  The proxy correctly sends the
X-Forwarded-For header lines to indicate the original requestor, so in
the bad-old-days, I built my combined logs with:

LogFormat "%{X-Forwarded-For}i %l %u %t \"%r\" %>s %b \"%{Referer}i\"
\"%{User-Agent}i\"" combined

Now...  how do I get out of the bad-old-days?  Section 3.6.17 of the
version 1.18 documentation (I'm using Apache 1.3) doesn't mention the
X-Forwarded-For header, nor is it mentioned in the equivalent unnumbered
section of the docs for 2.0.  I also can't find anything that would
allow me to specify additional headers myself.

Am I missing something obvious, or am I really making a feature request?
Given the benefits of mod_log_sql for aggregating the log data of a farm
of web servers, support for X-Forwarded-For would seem like an obvious
requirement.  :)

======================================================================

----------------------------------------------------------------------
 urkle - 04-16-05 16:28 
----------------------------------------------------------------------
e-mail from Michael Bourquin

we need to add a Load balancer in front of the network... The load
balancer will send an 'X-Cluster-Client-Ip' header. The remote_host field
will be the Load balancer IP.We need to retrieve the 'X-Cluster-Client-Ip'
and place into remote_host in the DB or in a new field.We would like to
know if it's possible to make this modification for us, because it's
necessary to have the real IP in the remote_field.

----------------------------------------------------------------------
 urkle - 04-16-05 16:41 
----------------------------------------------------------------------
The header can be logged within the headersin table (LogSQLWhichHeadersIn)
but a simple join must be done with the main log table and the headers
table on the UniqueID field (LogSQLLogFormat I) via mod_unique_id.

Another solution is to modify the mod_log_sql.c file around line 469 and
modify the log_sql_register_item line to call a function that will extract
the header similar to the extract_referer function in functions.h.. 

A better long term solution is for me to finish up my rewrite of the
logsqllogformat command to allow customization of the SQL database table

Issue History
Date Modified  Username       Field                    Change              
======================================================================
09-05-04 12:16 urkle          New Issue                                    
09-05-04 12:16 urkle          Apache Version            => unspecified     
09-05-04 12:16 urkle          Status                   new => assigned     
09-05-04 12:16 urkle          Assigned To               => urkle           
04-16-05 16:28 urkle          Note Added: 0000038                          
04-16-05 16:41 urkle          Note Added: 0000039                          
======================================================================




More information about the Issues mailing list