Search code examples
asp.netnetwork-programmingwiresharkf5

Need explanation on small length frames in wireshark


I see the following trace in wireshark when downloading an image form my .Net application.

What puzzles me is the sequence of 1514 bytes frame, followed by 61 bytes frame.

The image is streamed by an handler (ashx) of a .Net application which sits behind an F5. Chunking option on the F5 is set to RECHUNK.

Assuming there is enough information (my networking level being very low), here are my questions :

  • Is this expected network behavior?
  • If not, does it hinder network performance?

wireshark trace


Solution

  • The small length frames went away by selecting Response Chunking : Selective in the Http profile on the F5

    https://devcentral.f5.com/articles/ltm-http-profile-option-response-chunking

    I still don't know what was the root cause of the problem