[squid-users] 2.7.9 to 3.5 CentOS No-Cache

Tory M Blue tmblue at gmail.com
Fri Feb 13 00:24:40 UTC 2015


Greetings all, been a bit.

So I'm working on a new server config and loaded the latest 3.5 and have
tweaked my 2.7 configs a bit. Things are working but I've got one that I
can't figure out.

I have a test that insures that objects with an explicit "
Cache-Control: no-cache" header are NOT cached by Squid. This is done by
keeping a special hit counter on the server and counting origin requests. A
unique URL is fetched exactly 10 times, and all of them are asserted to be
cache misses (both Squid headers must be MISS). At the end, the hit counter
is tested and made sure it equals the number of requests (10)."

I'm getting a fail when testing against 3.5, meaning it's providing a cache
object

Miss with no-cache                  | FAIL    <------


Running test: Miss with no-cache...
Resetting hit counter...
Fetching URL:
http://10.13.5.222/admin/squid_test.php?action=reset_hit_count&random=0.385536803712753
HTTP 200: 200 OK
X-Cache: MISS from dev-centOS
X-Cache-Lookup: MISS from dev-centOS:80
Fetching URL:
http://10.13.5.222/admin/squid_test.php?action=simple&type=no_cache&random=0.0843643311677589
HTTP 200: 200 OK
X-Cache: MISS from dev-centOS
X-Cache-Lookup: MISS from dev-centOS:80
Fetching URL:
http://10.13.5.222/admin/squid_test.php?action=simple&type=no_cache&random=0.0843643311677589
HTTP 200: 200 OK
X-Cache: MISS from dev-centOS
X-Cache-Lookup: HIT from dev-centOS:80 *<—— Shows a hit (this should be 10
misses , a hit should never happen)*

*Test fails*

w/ 2.7.9 config
Miss with no-cache                  | Pass

Running test: Miss with no-cache...
Resetting hit counter...
Fetching URL:
http://devcache01.eng.admission.net/admin/squid_test.php?action=reset_hit_count&random=0.671442807268036
HTTP 200: 200 OK
X-Cache: MISS from dev-cache
X-Cache-Lookup: MISS from dev-cache:80

*I get 10 of the above responses (test passes).*

I'm wondering what I'm missing, 3.5 should be fully http 1.1 compliant
meaning that there should not be any squid directives guiding this (nor can
I find any). If the client sends a "Cache-Control: no-cache" it should be
honored natively ya?

Thanks for any pointers

Tory
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20150212/d8674e56/attachment-0001.html>


More information about the squid-users mailing list