Packets not sent to server

 

Ok, turns out that if the server doesn't respond for a HTTP GET message, then the F5 doesn't send the subsequent GET messages. In general, unless a response for a GET is received from the server, the next GET from the client on the same TCP connection is queued up. I don't use a one-connect profile but use an HTTP profile. This seems to be the behavior whether the 'pipelining' option in the HTTP profile is enabled or not. BTW, if I have a TCP-rule without an HTTP profile, the GET messages are sent right away even if the server doesn't respond to the first GET.

 

So, if I want to use HTTP profile can I force the appswitch to send the GET messages on the same TCP connection without them getting queued up using the iRule?

 

 

Thanks