maintaining persisitance between http and https sessions

You can use the match across services option for source address persistence, or an iRule like the one below for cookie persistence:

 

 

SOL5837: Match Across options for session persistence

 

https://support.f5.com/kb/en-us/solutions/public/5000/800/sol5837.html

 

 

Cookie encryption across pools and services

 

http://devcentral.f5.com/wiki/default.aspx/iRules/Cookie_Encryption_across_pools_and_services.html

 

 

Aaron

im confused on the cookie irule.. do you mind elaborating on the sample given....

 

 

coz one of the clause it says " All virtual servers must have an HTTP profile and a default pool"

 

 

what http profile is this referring to ?

 

 

Both the HTTP and HTTPS virtual servers must have an HTTP profile. The HTTPS virtual server needs to have a client SSL profile so that LTM can decrypt the SSL and then use an HTTP profile to parse the HTTP headers. The HTTP profile can be any HTTP profile--even the default HTTP profile. These configuration options are necessary to allow LTM to insert and subsequently parse the cookie used for persistence.

 

 

Aaron

okie.. i've copied the entire irule and it seems to be working..

 

but does the irule mention that it will create a cookie, if it's found different or non-existance ?

 

 

im not a programmer..dun really know how to interpret the irule :-)

Good to hear it's working for you. This command in the HTTP response inserts the cookie on every response:

 

 

HTTP::cookie insert name "BIGIP_COOKIE" value [IP::remote_addr] path /

 

 

Aaron

thanks...it did work according to the tester.. 'fingers crossed' its waht they need :-)