On 21/04/22 00:24, Garbacik, Joe wrote:
When squid connects to an upstream cache peer, does it create a new
tcp session between the peers for each request from a client on the
original squid server or does it maintain the session between the
peers for a period of time to allow other requests via the
established session?
FYI; TCP has connections, not sessions. There is a subtle difference but
very important in that it limits what can be done by other protocols
using TCP as a transport.
The answer to your questions depend on a lot of things...
Squid supports HTTP persistence and pipeline to both clients and peers
independently by default. For details on how those work see
<https://datatracker.ietf.org/doc/html/rfc7230#section-6.3>
<https://datatracker.ietf.org/doc/html/rfc7230#section-6.3.2>
Specifically, use of the features requires that;
* the peer also supports them, and
* your squid.conf has not disabled them, and
* your squid.conf has not enabled features that require them to be
disabled, and
* the traffic has not forbidden them, and
* the the messages going through allow them.
Amos
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users