cache deny all
Eric Oberlander <[email protected]> Wed, 6 Mar 2013 21:29:04 +0000
| Newsgroups | gmane.comp.security.ipcop.devel |
|---|---|
| Message-ID | <CAPkz44G2wYQDvxFZoKbdO6PJ8LmGerOdNJprKkZXkbDUMLcXvA@mail.gmail.com> |
Hi
Following Todd Wiegel's report on the ipcop-user mailing list that he was
unable to turn off caching, I had a look at the code in the
makesquidconf.plscript and there is a line that should print "cache
deny all" if this test
fails:
if (($proxysettings{'CACHE_SIZE'} > 0) || ($proxysettings{'CACHE_MEM'} > 0))
ie, both CACHE_SIZE and CACHE_MEM have to be 0 to turn off caching
But there is error checking in proxy.cgi that prevents CACHE_MEM being less
than 1
So, at the moment, I think "cache deny all" is broken.
What's the best way to repair? Allow a zero for CACHE_MEM? What might that
break?
The Admin Manual refers to turning off harddisk caching with a 0 in
CACHE_SIZE, but it doesn't mention CACHE_MEM, so perhaps the fix lies in
the makesquidconf.pl script?
Eric
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
IPCop-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ipcop-devel