Hi Amos, Alex,
--
Reading your conversations, here is a table of rules for pinning.
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_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
