Thanks!  These are good places to test.

> -----Original Message-----
> From: Paul Singleton [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, October 10, 2006 3:06 PM
> To: Tomcat Users List
> Cc: [EMAIL PROTECTED]
> Subject: Re: AOL
> 
> Daniel Blumenthal wrote:
> > We just switched from a single server to a cluster, with a load 
> > balancer out front to manage incoming connections.  The 
> load balancer 
> > makes the decision to go to app server 1 (app1) or app 
> server 2 (app2) 
> > based on IP address - once a request comes in from one 
> source IP, all 
> > future requests (for some period of time) go to the same server.
>  >
> > The problem is that it appears that AOL will randomly assign an IP 
> > address to every request a user sends.
> 
> They presumably run a proxy farm: the IP addresses from
> 
>    request.getRemoteAddr()
> 
> should be those of the (last) proxy which handled the request.
> 
> AOL should use the HTTP_X_FORWARDED_FOR* header to convey the 
> originating IP address (do they?): you could get this with
> 
>    request.getHeader("HTTP_X_FORWARDED_FOR")
> 
> IMHO if your load balancer switches on RemoteAddr when an 
> HTTP_X_FORWARDED_FOR address is available then it is broken, 
> and if AOL don't set HTTP_X_FORWARDED_FOR then they are 
> guilty of Bad Practice (only those dodgy anonymising services 
> have a good reason to do that).
> 
> Paul Singleton
> 
> * or perhaps HTTP_CLIENT_IP
> 
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org To 
> unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 



---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

  • RE: AOL Daniel Blumenthal

Reply via email to