[squid-users] server persistent connections and cache

[Vishali Somaskanthan]

Hi Amos, Alex,

Reading your conversations, here is a table of rules for pinning.

*STEP 1* *STEP 2* *STEP 3* *EXPECTED* *IMPLEMENTED*
BUMP - - NO PIN NO PIN
PEEK BUMP - PIN PIN
PEEK STARE BUMP PIN PIN
PEEK PEEK BUMP PIN PIN
SPLICE - - PIN PIN
PEEK SPLICE - PIN PIN
PEEK PEEK SPLICE PIN PIN
PEEK STARE SPLICE PIN PIN

PS:

No pin refers to - Would mean the connection to server will be pooled and
available for re-use for a different client connection. For splice, the TCP
connection to server is available for re-use. For bump, the SSL+TCP is
available for re-use.

Pin - Would mean shared fate for both connections.

2. Can you provide an example where NOT PINNING and not having the shared
fate breaks *fewer transactions*??

3. Is Pinning maintained at SSL level?? When the connection is pooled, do
you save SSL session states ??

4. We are looking forward to do an optimization where the same
TCP connection from squid to server is re-used for multiple requests from
client. Will that be a valid process with squid??



-- 
Regards,
Vishali Somaskanthan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20180730/89bc1915/attachment.html>