I have created a simple setup in order to do an HTTP/3 (on the client side, only) performance testing using F5 BIGIP on AWS.
TG (simulates client, sends HTTP/3 traffic) --> F5 BIG IP (HTTP/3 virtual server) --> Backend (servers are simulated by my TG tool, handling HTTP/1.1 traffic).
In F5 i have an HTTP/3 virtual server (based on UDP, since QUIC protocol is built on top of the UDP)
After capturing several traces, i am noticing that on the backend, where i'm handling HTTP/1.1 traffic, connection re-use is not working (after each GET request the connection closes, and opens up a new one) and therefore i'm really low on performance. I can't enabled OneConnect feature on my HTTP/3 virtual server (this option is not available)
So, regarding my question, is there any way i can enable connection re-use on the backend?
Bug ID 694511: The Virtual Server GUI page may allow misleading HTTP/2 configurations "The virtual will only use HTTP/1 to talk to the server, unless a http2 profile is used on the server side and a httprouter profile is attached."
In order to use http/2 to the backends you must enable server http/2 profile and "Select the HTTP MRF Router check box." Look also K60235402: Overview of the BIG-IP HTTP/3 and QUIC profiles
