Cookie encryption issues?

If I disable the source_addr fallback persistence, I do seem to get the same pool member within the same session. And different pool members across different browsers originating from the same source address. Where as when I turn source_addr fallback on, I get the same pool member across all browsers.

 

Why would it use the fallback profile? I thought it is only supposed to use the fallback ONLY if the default does not function?

 

 

EDIT: I think I have a bit more testing to do actually. The production method of encryption is different than that of test. Test is using an iRule:

 

 

when RULE_INIT {

 

set ::key [AES::key 128]

 

}

 

when HTTP_RESPONSE {

 

set decrypted [HTTP::cookie "BIPxxxx-http"]

 

HTTP::cookie remove "BIPxxxx-http"

 

set encrypted [b64encode [AES::encrypt $::key $decrypted]]

 

HTTP::cookie insert name "BIPxxxx-http" value $encrypted

 

}

 

when HTTP_REQUEST {

 

set encrypted [HTTP::cookie "BIPxxxx-http"]

 

HTTP::cookie remove "BIPxxxx-http"

 

set decrypted [AES::decrypt $::key [b64decode $encrypted]]

 

HTTP::cookie insert name "BIPxxxx-http" value $decrypted

 

}

 

 

where my test setup is using http-cook-enc http profile. With production, when I turn off the fall-back source_addr persistence, there seems to be NO persistence.