Martin,
> If I go to www.AOL.com I am on their web-server
Yup. We're not talking about going to www.aol.com. We're talking about
AOL customers browsing this dude's application, which is not hosted
through AOL.
> and if I check email I am submitting the request thru those sa
Chris-
If I go to www.AOL.com I am on their web-server and if I check email I am
submitting the request thru those same web servers
If YOU can guarantee ME that they ARE NOT redirecting then as a way to handle
the special processing for aol you could do something simple like check the
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:
> >
Martin,
Apparently, your mail reader seems my messages as blank (due to poor
handling of GPG attachments). Here is the message I was trying to send:
> Dude, I think you're totally confused.
>
> You can replace the term "AOL" in all of these messages with "some
&
Tuesday, October 10, 2006 3:08 PM
Subject: Re: AOL
Martin,
> Saying you'll only deal with the first n addresses may lead to bigger
> problems later on.. I would put a sniffer on to see if AOL is giving
> you a 301/302. If that is the case you will have to configure
> variables Cache-Control Expires
Dude, I think you're tota
, 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) pr
Dan-
Saying you'll only deal with the first n addresses may lead to bigger problems
later on..
I would put a sniffer on to see if AOL is giving you a 301/302
If that is the case you will have to configure variables
Cache-Control
Expires
Martin--
This e-mail communication and any attach
Daniel Blumenthal wrote:
How does the lb decide where you go for all requests after
the first one? Typically, the session id is sniffed from the
URL or cookie and the lb maintains a table of mappings that
expires after some time.
Our two choices are evidently "IP-based" and "cookie-based".
Dan,
> Our two choices are evidently "IP-based" and "cookie-based".
> Currently, we're using "IP-based", so every IP address is treated as
> a separate request. I'm looking into making it cookie-based, and
> making cookies a requirement for the site (currently, we only use
> cookies to store a co
Daniel Blumenthal wrote:
Chris,
How does the lb decide where you go for all requests after
the first one? Typically, the session id is sniffed from the
URL or cookie and the lb maintains a table of mappings that
expires after some time.
Our two choices are evidently "IP-based" and
a lot of data going
> into the session, I would imagine that it isn't too chatty on
> the backend.
>
> When consulting for [a large robber baron in the SSL cert
> racket], their setup was to actually divert all of their AOL
> customers away from the main cluster and onto
Dan,
> The problem is that it appears that AOL will randomly assign an IP
> address to every request a user sends. So a user could end up going
> to both servers.
Yup. AOL is feisty like that.
> The load balancer makes the decision to go to app server 1 (app1) or
> app server
Martin,
I think there might be a bit of a misunderstanding - America Online (AOL)
isn't a server under my control - it's an ISP from which some of my
customers come.
Daniel
> -Original Message-
> From: Martin Gainty [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, Octob
Good Morning Dan-
It seems you're going thru alot more work because of session expiration issues
Do you know if AOL supports 'sticky' sessions?
Thanks,
M-
This e-mail communication and any attachments may contain confidential and
privileged information for the use of the
design
Good morning Martin,
Have I misunderstood? The issue isn't switching from using Apache as a
front end (for now), but rather that America Online (AOL) uses proxy banks,
so that every request comes in with an arbitrary IP address. This is
causing two problems:
1) Users are logged in on
Good Morning Dan
From what I see alot of folks are using Hardware accelerators to overcome
inherent delay introduced by front ending with apache
To clarify everyone's understanding
What does AOL bring to your environment and How does AOL server configure in
your environment?
If I h
, 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. So a user could end up going to both
servers.
You should configure load balancer to use 'sticky sessions' (
nt 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
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. So a user could end up going to both
servers.
With the exception of user login data, the code is reentrant, but I've had
to store login inform
20 matches
Mail list logo
