Last Modified: Oct 06, 2023
Known Affected Versions:
16.1.0, 16.1.1, 16.1.2, 220.127.116.11, 18.104.22.168, 16.1.3, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11
17.1.0, 16.1.4, 15.1.9
Opened: Feb 14, 2022 Severity: 3-Major
When clientside is using HTTP1.1, serverside is using HTTP2 and two HTTP GET requests are sent by the client, BIG-IP completes the first HTTP transaction and sends a FIN, even though HTTP keepalive should be enabled.
Premature TCP connection termination on the clientside.
-- HTTP2 full proxy is configured i.e. http profile, http2 profile and MRF router is enabled. As per https://techdocs.f5.com/en-us/bigip-14-1-0/big-ip-http2-full-proxy-configuration-14-1-0/http2-full-proxy-configuring.html -- clientside uses HTTP1.1. -- serverside uses HTTP2. -- Two subsequent GET requests are sent by the client.
Disable the MRF router (httprouter). The drawback is that serverside will always use HTTP1.1 in this case and it might be undesirable if you want to leverage HTTP2.