For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Jérôme_ANGLES's avatar
Jérôme_ANGLES
Icon for Nimbostratus rankNimbostratus
Nov 25, 2014

Delay between two HTTP requests in a common TCP.flow (between 10 - 30 seconds)

I have a long wait on a application configured on a bigip LTM 3900 v10.2.2. I captured the traffic on the bigip and there are a few things i see that seems strange...   On a common tcp.flow, th...
application delivery
design
LTM
performance
giltjr's avatar
giltjr
Icon for Nimbostratus rankNimbostratus
Nov 27, 2014

Depending on how much content is downloaded and the bandwidth available between the F5 and the client, there will be a delay in seeing the HTTP response on the client. It may take 10-30 seconds for the response to get to the client, so the client will see a 10-30 second delay.

 

If you are using a port other than 80 for HTTP traffic, Wireshark will not interpret the traffic as HTTP and thus will not show HTTP request/response. In Wireshark you can go to Edit/Preferences/Protocols, then select HTTP and add what ever ports you are using for HTTP traffic. I am assuming you are using 16073 since this is one of the ports you are capturing traffic on.