For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

RajaShajeelAhmed's avatar
RajaShajeelAhmed
Icon for Cirrus rankCirrus
Feb 07, 2024

HTTP 1.1 concurrent to HTTP 1.1 Pipelining

What is the limitation in HTTP-1.1 TCP stream using concurrent connection? If we want to have multiple concurrent requests without waiting for the response to be completed in a TCP stream what to do?...
application delivery
Lucas_Thompson's avatar
Lucas_Thompson
Icon for Employee rankEmployee
Feb 08, 2024

I'd avoid HTTP pipelining if possible. It doesn't offer benefit over normal keep-alive in the context of reducing SSL handshakes. It's also somewhat rare to see in actual use, which increases the risk of incompatibilities between the client and server and the risk of vulnerabilities like request smuggling. Also it looks like Chromium doesn't support it.

Reducing SSL handshakes is the main purpose of BIG-IP's "OneConnect" profile, it allows re-use of already open TCP channels.

Here's a good post that discusses it:

https://wtit.com/blog/2019/09/24/understanding-f5-oneconnect/