Exception thrown on a re-connect to BIG-IP

Hi Joe,

 

 

Thanks for your reply. Appreciate it very much.

 

 

I had initially set PreAuthenticate to true. After seeing your post, I changed it to false…however, that didn’t help…I still get the exception. (the .net framework sdk only mentions that setting PreAuthenticate to true will cause the client to voluntarily present credentials….there is no mention of its effect on http keepalives. Are you deducing this information from experience or am I not looking at the right msdn documentation?).

 

 

Anyway, I did a packet sniff and found the following to be the cause of the exception:

 

During the wait, BIG-IP sends a TCP FIN to my windows box for the TCP connection opened prior to the wait. The windows box acknowledges the TCP FIN. However, the windows box does NOT send a TCP FIN or a TCP RST to close its end of the connection. Instead, after the wait, when I re-initiate contact, the windows box sends the data over the same TCP connection. BIG-IP responds to this with a TCP RST. I am pretty sure this TCP RST is what is causing the exception.

 

 

I did the packet sniff with and without setting PreAuthenticate. There was no difference with respect to the above behavior. However, there was more number of TCP connections when I set PreAuthenticate to false, which seems to validate your point about its relationship to keepalives. Given that the TCP payload is encrypted with SSL, I am unable to look inside the HTTP header to see if keepalive is enabled. Not that it would matter anyway.

 

Thanks,

 

Karthic.