[squid-users] server persistent connections and cache

[Vishali Somaskanthan]

Dear Squid users,
          There is a connection C1 from the client to squid and that is
bumped at squid which forms a TCP connection with origin server S1. Having
server persistent connection turned on, for subsequent requests, I see that
the same TCP connection is used between the squid and the server and all
was fine.

I had a problem after sending too many requests to the same server where my
persistence stopped working suddenly. The connection was getting closed
from the squid side sending a FIN packet to the origin server. When
debugging on this, I found my access logs had states
TCP_REFRESH_UNMODIFIED, instead of TCP_MISS which I was seeing earlier when
all was fine.

I found that the results were from cache. I included the  cache deny
all  option
and found that the access logs had TCP_MISS since it wasn't using
cached results and my persistence is fine again.

I have three questions in this scenario:
1. What is the relationship between the caching and the persistence
connection established?
2. When will squid use cached results and when will it not if the cache
deny all directive weren't specified.
3. However, this didn't work fully. Even with *cache deny all* directive,
persistence wasn't working when I peeked at the sslBump step 1 and then
Bumped.
Persistence worked only when I directly did sslbump allow all (without
peeking at first step).


Comments are appreciated on the scenario.



-- 
Thanks,
Vishali Somaskanthan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20180718/36b2ea79/attachment.html>