WebSphere Site Analyzer - Using X-Forwarded_For

This is Interesting: Free IT Magazines  
Home > Archive > WebSphere Site Analyzer > December 2004 > Using X-Forwarded_For





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Using X-Forwarded_For
DavidT

2004-12-28, 6:07 pm

Config:
- TWSA 4.5
- Websphere 5.02 with IBM HTTP Server
- Websphere Portal Server 5.0.2
- Windows 2003 Server

We have a web server that is behind a proxy. The access log and the
sa.log show all the ip addresses to be the same - as one would expect
from the proxy.
Therefore I have changed the IBM HTTP server httpd.conf LOGFORMAT to use
the X-Forwarded-For instead of the normal client host IP. This works BUT
we have a large proportion of these parameter coming through on the log
with 2 IP addresses e.g. "10.10.10.10, 10.10.10.11" (one IP followed
by another separated by a comma), which causes the Site Analyzer to
report invalid data.

1. Any suggestions how to resolve this problem of duplicate IP addresses?
2. If this can be solved then is the anyway to change the IP Address on
the sa.log for WebSphere Portal Server to use the X-Forwarded-For?

TIA
David
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com