> By all means, post the relevant portion of the log file. I don't think this is of big help here.
> It would be very helpful if you'd answer my earlier question about >how you take a request and route it to Velocity We put the request into the velocityContext and hence have the possibility to access "whe(r|n)ever needed" >How do you know that the requests are coming from certain IPs and they are >then being reported incorrectly in the access.log or in your own web pages. 1) in the access.log we see all requests 2) if a specific monitoring-URL is called from our monitoring site (which's IP we know ;) ), AND the IP does not "match the monitoring site", we write out the remote IP into the app-log as an error Now if the load on our site is high (bots accessing) then we frm time to time see these errors AND in the access.log we see that reported IP matches "the request before the monitoring request" (from the bot) Hope this helps -----Ursprüngliche Nachricht----- Von: Christopher Schultz [mailto:ch...@christopherschultz.net] Gesendet: Mittwoch, 12. März 2014 17:41 An: Tomcat Users List Betreff: Re: AW: AW: AW: request.getRemoteAddr() sometimes returning IP address from the previous request -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Clemens, On 3/12/14, 11:34 AM, Clemens Wyss DEV wrote: >> Do you have any proof of this or is this just guess work? > No guessing. Am taking into account apache's access-log and our > application logging. We log the IP (i.e. request#getRemoteAddress) of > sepcific requests into our application logs and from time to time see > the IP oft he "previous request" (access.log tells us that this is the > IP of the/a previous request) By all means, post the relevant portion of the log file. How do you know that the requests are coming from certain IPs and they are then being reported incorrectly in the access.log or in your own web pages. It would be very helpful if you'd answer my earlier question about how you take a request and route it to Velocity. You may be making serious mistakes when you do that which could be the root cause of these problems. You are unlikely to be able to break the access log, even if you break your own application. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTII4lAAoJEBzwKT+lPKRYYskP/0K/mo6m/TOu5UmfmKAeoIMV uuuNgQSFms8c/ufad+b/kywDt//TcPuu9fUsOMJmFuoMEoK4iI+xKTTApb/fuii5 yA2p8XD/qnRM227RSoquITn9WCsiTLfW9Eu/Hm5/VP9lPJ46yKX3QiEiz2xXPtZh rp5nD22QTulmX+WrNiAPXPd1Z+Dq4xQ8Uto/AU8TUGzjrl7J8IfftAbObYQyqtSo hdlB+gdYY/hvY/WifqmpHHd9eUv7ANzHTa3cKGPmWC6qR42XEaLL8qi5bcnfBPzr onRfANCBq1Qr70xA0P2l02ZQ1WpXIvEgOhkz+M5aQr0myC7MBnTUoymzXXZdkFwo R2Xcj1wC2byHstWlxWIm1ieGrH60iR+krYVNog8JUJ3WCLR3NYCaX2dM/ZGB2dk7 FhpK2OulLKNQUq9WMVEgoTUeGiuxWzurrIXriarQDKPoajjCm2Bw3+ODtC9jxy8H AVFb03E60pdUGDBxq0HOr8A4N9v4sYlbWz69b3lbv5jFlqVKfd4n06sK5hOxxcUE jxQd26m/XwaQ0cYV93r0fb7ygoPxHwmDuK7OC1QuciCraqpbkE94CHuKmIHzD/p4 oz2rf2JVdRWszr+s8HQ6KnyB7uN7D5mnxTZhXJTTGsc3BV+38nA+gLDRHY6yFHIN BcDnVbvH25WtcYxsHsJV =ungh -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
