Tell me if I'm wrong, sessions variables aren't stored in browser (I mean
client side) in the form of a cookie? By the way, we have an other problem
we need to publish dynamic content ( a perl script that build web page), to
solve that problem the solution was to make the master server post the
dynamicly builded page to other server, that way we ensure perfect
synchronization... but that didnt solve your problem if it was one.. keep us
informed if you find something interesting.
emman
----- Original Message -----
From: "Madhav" <msp@xxxxxxxxxxxx>
To: <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Thursday, April 06, 2000 3:31 AM
Subject: problems with LVS for http service.
> hi,
> We have set up LVS-NAT with heartbeat and mon with 2 real servers. We
> configured lvs to provide http, ftp and telnet services. For each request
> from the client for http service, the request is routed to a different
> realserver alternatively.
> I have an HTTP application where in page1 the login name is accepted and
> this is stored in the web server as session variable. During subsequent
> navigations in the application this session variable is made use of. This
> works fine if i use only one real server for http service.
> But in LVS, page1 is serviced by a realserver (say RS1) and the subsequent
> navigations may be routed to other realservers(say RS2) where the session
> variable is not available.
>
> Has anybody else come across these problems?
> i do not want to change my application. is any solution available for this
> problem?
>
> Thanks
> Madhav
>
>
>
>
|