Re: Issues with getRemoteAddress

2011-05-31 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Filippo, On 5/27/2011 4:21 AM, Filippo Machi wrote: we have a filter, not a valve, (a class implementing javax.servlet.Filter) that authenticates incoming request according to: - a particular key contained as parameter in the request - the ip

Re: Issues with getRemoteAddress

2011-05-27 Thread Filippo Machi
Ciao Andrè, thanks for your answer! I really appreciate all the time you spend, thanks again. Please find my inline answers.. On Thu, May 26, 2011 at 7:12 PM, André Warnier a...@ice-sa.com wrote: Hi. First, tell us what precise version of Tomcat you are using (x.y.z format). we're using

Re: Issues with getRemoteAddress

2011-05-27 Thread André Warnier
Filippo Machi wrote: we're using tomcat 7.0.12 Ok. 1) You have serverA running Tomcat, and Tomcat listens on port 8080. The (network) IP address of serverA is : 85.214.x.x (apart from the loopback address 127.0.0.1) This Tomcat has some IP-based access Valve which : we have

Re: Issues with getRemoteAddress

2011-05-27 Thread Filippo Machi
On Fri, May 27, 2011 at 11:20 AM, André Warnier a...@ice-sa.com wrote: Filippo Machi wrote: we're using tomcat 7.0.12 Ok. 1) You have serverA running Tomcat, and Tomcat listens on port 8080. The (network) IP address of serverA is : 85.214.x.x (apart from the loopback

Re: Issues with getRemoteAddress

2011-05-27 Thread André Warnier
Filippo Machi wrote: On Fri, May 27, 2011 at 11:20 AM, André Warnier a...@ice-sa.com wrote: Filippo Machi wrote: we're using tomcat 7.0.12 Ok. 1) You have serverA running Tomcat, and Tomcat listens on port 8080. The (network) IP address of serverA is : 85.214.x.x (apart

Issues with getRemoteAddress

2011-05-26 Thread Filippo Machi
Hi all, we're experiencing an issue with the getRemoteAddress method (HttpServletRequest). We don't know whether is something known depending on tomcat or if it's something malicious, affecting our servers. We have a filter that authorizes incoming requests using different patterns, one of these

Re: Issues with getRemoteAddress

2011-05-26 Thread André Warnier
Hi. In addition to what you explained below, could you explain the network setup ? In particular, are users always accessing the tomcat server directly, or through a firewall, and/or through a front-end like Apache httpd ? And what is this external service ? is that another webserver ? On what

Re: Issues with getRemoteAddress

2011-05-26 Thread Filippo Machi
Ciao André! Thaks for your answer. Let me add some further info. The service I was talking about is a php script we put in the crontab and it accesses directly to the tomcat asking the url (127.0.0.1:8080/...) I'm omitting the final part of the ip just for privacy. There are just a little set of

Re: Issues with getRemoteAddress

2011-05-26 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Filippo, On 5/26/2011 8:22 AM, Filippo Machi wrote: The service I was talking about is a php script we put in the crontab and it accesses directly to the tomcat asking the url (127.0.0.1:8080/...) Okay: when you use 127.0.0.1, you should always

Re: Issues with getRemoteAddress

2011-05-26 Thread Filippo Machi
Ciao Christopher, we don't trust 85.18.x.x., it doesn't belong to us, that's why I posted my question. We're not able to explain how is possible that a request from localhost to localhost appear to be issued from a different ip. Anyway, I'm going deeper following your hint about the rewrite. May

Re: Issues with getRemoteAddress

2011-05-26 Thread André Warnier
Hi. First, tell us what precise version of Tomcat you are using (x.y.z format). Then, one minute I think that I am starting to understand your setup, but the next minute I am lost again. The way I understand it now (please correct whatever needs to be) : 1) You have serverA running Tomcat,

Re: Issues with getRemoteAddress

2011-05-26 Thread Pid
On 26/05/2011 15:43, Filippo Machi wrote: Ciao Christopher, we don't trust 85.18.x.x., it doesn't belong to us, that's why I posted my question. We're not able to explain how is possible that a request from localhost to localhost appear to be issued from a different ip. If it's not one of