bad ssl sessionid containing null byte

We've determine why the problem occurs and we now have a hotfix available for this. Reference CR57247.

 

 

So, this leave you with two options.

 

 

a) truncate the null byte off the end and go with the first 31 bytes. If the bigip is terminating the ssl, then this will actually be alright because of the way the bigip generates the session id. You are guaranteed not to encounter the same first 31 bytes in a session id for about 65 years.

 

 

b) get the hotfix from support.

 

 

Hope that helps.