NimbostratusI am using a TCP profile for a Standard VS along with HTTP and, SSL server and client side profiles. I have a few questions when I looked into the client side capture from F5. 1. In the SYN ACK packet, why is Window size advertised by server is always around 5000 bytes, even though the send buffer and proxy are set to 64k ?
Nimbostratus(Question continued...F5 ASM blocked this following part as SPAM so I couldnt post above.) 2. Server sends a FIN ACK after transmitting the data, and client responds with an ACK to that. But client takes ~800ms to send the FIN ACK to F5. Is this because Client is processing the received data or is it waiting for more data from server(Which it shouldn't, since F5 has already send FIN ACK)? 3. After a small transaction, of around 15000 bytes, f5 opens a new session with different port number on the client, and the handshake process takes around 1 sec to complete. Can I configure the F5 to keep re use the previous session.(To skip the handshake transactions and the session close transactions)? EX: Session 1{51477->443SYN , 443->51477 SYN ACK WIN =4200, 51477->443ACK, Client Hello,Server Hello, Certificate, server hello Done, 51477 > 443 ACK,Client key exchange ,443 > 51477 ACK WIN =4800...>Application dataTill here it takes 2.5 s, and again for closing it takes 800ms., and in no time it starts a new tcp connection with different port number on client.} How to optimize this? on.(To skip the handshake transactions and the session close transactions)?
NimbostratusAny F5 gurus?