Nino, I'm thrilled that you onto the problem, and that there definitely
seems to be a real issue, its not just a config glitch somewhere. but it
doesnt look good.
That command is effectively turning Apache into a steam engine on windows,
and its treating windows like its got stone age sock
- Original Message -
From: "Nino Ulsamer" <[EMAIL PROTECTED]>
To: "Tomcat Users List"
Sent: Tuesday, July 03, 2007 2:25 PM
Subject: AW: Tomcat - Apache: IP replacement
Hi,
thanks for your help!
I now tried the following: I set up the configuration as you told me on my
local machine
Hi Nino,
Just to make sure my memory served me correctly, I setup a test case for
Apache -> JK -> TC on a machine (XP SP2) with IPV6 enabled.
Apache, Browser and TC... are all on same machine to simulate your test.
Apache is not IPv6 enabled
The machines name is Animal ipv4 10.0.0.4... IP
article from when the TC guys where
messing around with it... http://www.junlu.com/msg/354211.html
---
Thanks,
Nino
-Ursprüngliche Nachricht-
Von: Johnny Kewl [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 2. Juli 2007 13:21
An: Tomcat Users List
Betreff: Re: Tomcat - Apache: IP replacement
Ha ha you made me panic, no my load sharing stuff behind JK, is not
doing that, ie getRemoteAddr is working.
You know if you on a MS box, (guessing wildly here), the first time I ever
saw 0.0.0.0 as a local address is when I was playing with IPv6.
and only on the "local" IPV6 addresses,
I had an issue where getLocalAddr() would return 127.0.0.1 rather than
the ip address of my linux box. Altering the /etc/hosts file to
something like the following fixed that. I wonder what effect that
might have for your problem.
192.168.6.173 box box.domain.com
127.0.0.1
Something is wrong with your configuration or box setup.
request.getRemoteAddr() works for me, it shows the Apache server address
used by the request.
Regards,
Rainer
Nino Ulsamer wrote:
Hello,
I have a problem with finding out the IP address of requests in Tomcat.
I'm using the HttpServlet