F5 FastL4 but need HTTP header insert

If you care less about compression on the client side of the WAN, then you should disable it completely on the appropriate VIP(s) on the BIG-IP, and leave the compression to the remote load balancers; that would also send fewer bytes across the WAN link.

 

 

This indeed what we did; it is probably what is occuring now; and may explain some of the speedup when compression is off.

 

 

On the other hand, I am sorry to say, we verified that the content is uncompressed, even if we ask for it with the "compress disable" option. I have no idea if it is compressed on the backhaul from the origin load balancers.

 

 

I'm a little surprised that FastHTTP wasn't working for you, though, as it comes closest to "fastL4 + header insert", but you didn't mention how it didn't work. If it also showed the same bad latency, then that would almost certainly point to misconfiguration or other problems outside the BIG-IP. That said, FastHTTP is optimized for ideal conditions, which you may not find in your network.

 

 

I was looking through my notes and emails and trying to get some more details. Unfortunately, my recollection is a bit sketchy. At best, I remember that it did not seem to perform as well, but that could be lack of experience at the time (first time setting it up back then).

 

 

What would be perfect for this scenario is to get an example configuration that I could try; I have access to some testing VIPs and can provide a lot more information if I have a starting point.

 

 

Could someone post a code snippet for FastHTTP that might work with header inserts of client IP?