Re: Cookie Persistance
Kenneth Salchow <[email protected]> Wed, 1 Jul 2009 06:20:27 -0700
| Newsgroups | gmane.comp.programming.load-balancing.general |
|---|---|
| Message-ID | <4B18A8F75A6384449755BC7784073E9360CF2165D0@exch11.olympus.f5net.com> |
BTW--you might also want to see if you can apply encryption to those cookies at the ADC--whether generated by the ADC or the server. Especially if you're using something like JSessionID from the server. It's a fairly simple thing that can dramatically increase your overall security posture. KJ (Ken) Salchow, Jr. | Manager, Technical Marketing D 651.423.1133 M 612.868.12588 P 206.272.5555 F 206.272.5555 www.f5.com -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Ravi Kumar Sent: Wednesday, July 01, 2009 1:35 AM To: [email protected]; Load Balancing Mailing List Cc: Load Balancing Mailing List Subject: Re: [load balancing] Cookie Persistance Thats right. But the solution to choose will depend on your web server. I heard cases where webserver will not like the ADC/LB devices inserting its cookie. In that case, let the web server generate its cookie and LB will do passive cookie persistency. Well, there are some LBs that removes its inserted cookie before sending it to the servers. Then, those LBs are perfect and has no problems with the web server. -Ravi. http://netlb.blogspot.com > Most LB products including WSD support cookie insert mode. You don't need > the server to create cookies for you, though that is always an option. > Certainly the mainstream LB such as F5, NetScaler, and Alteon do, and > expect WSD and the various Ciscos do too. It's a very basic option these > days. > > There may be reasons why you do want to use a server-originated cookie > (jsessionid as an example) but you need to assess what your design goal > is across apps/ network and you are creating complexities/ additional > interdependancies between your servers and LBs > > The simplest and usually most robust solution is to just turn > cookie-insert mode on and let the LB do the smarts. > > Best regards, > > Andrew Cook - Principal Consultant > Smartworx - creating synergies between networks and applications. > 65 Hume Street, Crows Nest. NSW. 2065 Australia > t: +612 9016 2880 f: +612 9016 2881 m: +61 419 253 347 > email: [email protected] > web: www.smartworx.net.au > > Sent via BlackBerry® from Vodafone > > -----Original Message----- > From: Maheshwari <[email protected]> > > Date: Sat, 27 Jun 2009 23:04:28 > To: Load Balancing Mailing List<[email protected]> > Subject: Re: [load balancing] Cookie Persistance > > > _______________________________________________ > lb-l mailing list > [email protected] > http://vegan.net/mailman/listinfo/lb-l > Searchable Archive: http://vegan.net/lb/archive > http://lbdigest.com Load Balancing Digest > http://lbwiki.com Load Balancing Wiki > > _______________________________________________ > lb-l mailing list > [email protected] > http://vegan.net/mailman/listinfo/lb-l > Searchable Archive: http://vegan.net/lb/archive > http://lbdigest.com Load Balancing Digest > http://lbwiki.com Load Balancing Wiki > > > _______________________________________________ lb-l mailing list [email protected] http://vegan.net/mailman/listinfo/lb-l Searchable Archive: http://vegan.net/lb/archive http://lbdigest.com Load Balancing Digest http://lbwiki.com Load Balancing Wiki _______________________________________________ lb-l mailing list [email protected] http://vegan.net/mailman/listinfo/lb-l Searchable Archive: http://vegan.net/lb/archive http://lbdigest.com Load Balancing Digest http://lbwiki.com Load Balancing Wiki
smime.p7s
(application/x-pkcs7-signature, 3 KB) - not displayed