Encrypting Cookie Produces Numerous Cookies

If anyone is interested...I found a quick fix around the firefox issues.

 

So, we had to implement this cookie encryption today...but we really didn't want to take the chance of upgrading to 9.4.x so we used the iRule listed above until we can get the upgrade done.

 

Anyways, when you put this iRule into play, firefox users get a connection refused since they still have the old cookie loaded up (old cookie isn't encrypted and thus BigIP doesn't know how to read it). What we did was rename the cookie first in the iRule...so when you head over to the site it generates cookies from the BigIP, but these cookies are not yet used for anything. After that we created a new cookie persistence profile with the new cookie name. After that we switched the site over to the new cookie persistence with the cookie name the same as the encrypted cookie name and presto! all users can connect.

 

This is a bit of a daisy chain...but we can't exactly ask all users to clear their cookies just to connect.

 

Thought this might help someone.