Client SSL Insert

This may sound a little bizzare, and will eventually be fixed in a future release. The session table actually utilizes the persistence table and as a result, some of the behaviors of the persist table have made there way into how the session table behaves. The issue that is getting you here is what's known as "persist across ...". Since the pool is different, persistence would normally not use the entry unless persist across services or persist across pools is enabled. Obviously, this really isn't appropriate behavior for the session table.

However, you should be able to easily work around it by changing your session lookup like so:

set certfields [session lookup ssl {[SSL::sessionid] any}]

Please let us know if this corrects your problem so we can get it fixed in a future release.

Thanks!