QUIC - HTTP/3 + F5 LTM + APM + WAF
Hi looks to me like HTTP/3 is coming to all, I like some of the features. But how do I get http/3 /quic and LTM + APM + WAF I get that http/2 is available and LTM only. I presume http/3 will be roughly the same. I'm guessing but if I want to could I create a VS with http3 and all it does it then reverse proxy to another VS and on the second VS I can do APM / WAF. internet -> VS / HTTP3 / LTM -> VS / HTTP1.1 / LTM /APM / WAF -> resource pool does that work does the second VS see the client ip - will APM work in that scenario ? When it http/3 going to be fully supported LTM/APM/WAF ?
Connection re-use on the backend with HTTP/3 virtual server
Hello Group, 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? Any suggestions would be great. Thanks in advance!
Problem with forward QUIC-serverside traffic to another VS
Hello! I have a problem with forward traffic from VS (QUIC-proxy) to another VS (content-switching, etc) on same BIG-IP (version 16.1). It's not working. If in the virtual server settings I set POOL directly to the backend-server - everything works fine. If i want forward requests to another VS on same BIG-IP (even if it's a completely empty VS) - QUIC doesn't work. I tryed with different types of VS ( all of them :( ), tcp-profiles, with and without SNAT, with irule/policies, with ssl offload/bridging, with http1.1/http2 - no more ideas, nothing help. Could I change this behaviour? Thanks a lot!