|
That will be a different cookie. Load balancer is
suppose to issue a cookie at the first time the
server was selected. In the future, it will keep
checking this cookie. That is why cookie persistent
is very slow and CPU intensive.
At 05:11 PM 10/4/00 -0700, Meijuan Feng wrote:
>So if cookies are already used for shopping cart info,
>does the load balancer modify this cookie and add a
>key for load balancing purposes?
>
>--- Wayne <wayne@xxxxxxxxxxxxxxx> wrote:
>> Of course you could. But without a SSL decoder
>> at the front, the cookie persistent will no do you
>> any good. Say you have 5 web servers both
>> provide the shopping cart, running HTTP and
>> HTTPS. Browser the cart is using HTTP, and
>> check out using HTTPS. If you have cookie
>> persistent that always send your request to server
>> 3 during the cookies life time. Once you click
>> on the check out, you were started using the
>> secure server. However, in the HTTPS, all the
>> cookies information are also encrypted, so the
>> load balancer may not send you to server 3 any
>> more. All the selection you had done for your
>> family Christmas shopping in last three hours
>> were gone! (actually, they still stay on server
>> 3, but you could be send to server 4 now).
>>
>> At 03:57 PM 10/4/00 -0700, Meijuan Feng wrote:
>> >So the idea of cookie persistence is to use cookie
>> >information stored by a client to direct the client
>> >connection to the appropriate server. But what if
>> the
>> >current connection is already using cookies for
>> >something else, such as keeping shopping cart
>> >information? Can cookies be used for persistence
>> and
>> >shopping cart information at the same time?
>> >
>
>
>__________________________________________________
>Do You Yahoo!?
>Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free!
>http://photos.yahoo.com/
>
|
