/usr/share/doc/sqcwa/README is in sqcwa 0.3-3.1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 | sqcwa -- workaround for squid not caching pages with
<meta http-equiv="pragma" content="no-cache">
or others
Copyright (C) 2003 Pedro Zorzenon Neto <pzn@autsens.com>
José Roberto Monteiro <jrm@autsens.com>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
--
This program reads squid/access.log, analyses it and searches inside
all text/html objects for some <meta> tags, and if found, tells
squidclient to purge the page.
This program is in TESTING stage.
To use it, install squid and squidclient in the computer, and
execute the following command:
sqcwa /var/log/squid/access.log
It will expect that you have installed the program client from squid
in /usr/bin/squidclient. If you do not have it there, then use a
symbolic link or change SQCLIENT.H in the sources.
It will expect to find squid running in localhost tcp port 3128.
Note: this program will only run if executed in the same
computer where squid is installed.
I'd apreciate your comments about this program. This is a TESTING
version and we need to know how it is working. Write to <pzn@autsens.com>
with subject sqcwa.
We tried to make this program without any security hole, but we are not
sure about it.
Known side effects of using it:
- increases CPU load (not too much. in out tests, less than 1%
in a pentium 2 300MHz, with 5 browsers using proxy)
- does not work if someone navigates from localhost
- increase access.log lines with accesses from localhost
(check and purge access)
SQCWA means SQuid Cache Work-Around
|