/usr/share/doc/adzapper/README.Debian is in adzapper 20090301.dfsg.1-0.2.
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 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 | Adzapper for Debian
===================
Squid support
=============
To use adzapper you must edit your squid.conf file. The following
piece in squid.conf needs to be set:
---
# TAG: url_rewrite_program
# Specify the location of the executable for the URL rewriter.
# Since they can perform almost any function there isn't one included.
#
# For each requested URL rewriter will receive on line with the format
#
# URL <SP> client_ip "/" fqdn <SP> user <SP> method <SP> urlgroup
# [<SP> kvpairs] <NL>
#
# In the future, the rewriter interface will be extended with
# key=value pairs ("kvpairs" shown above). Rewriter programs
# should be prepared to receive and possibly ignore additional
# whitespace-separated tokens on each input line.
#
# And the rewriter may return a rewritten URL. The other components of
# the request line does not need to be returned (ignored if they are).
#
# The rewriter can also indicate that a client-side redirect should
# be performed to the new URL. This is done by prefixing the returned
# URL with "301:" (moved permanently) or 302: (moved temporarily).
#
# It can also return a "urlgroup" that can subsequently be matched
# in cache_peer_access and similar ACL driven rules. An urlgroup is
# returned by prefixing the returned URL with "!urlgroup!".
#
# By default, a URL rewriter is not used.
#
#Default:
# none
url_rewrite_program /usr/bin/adzapper.wrapper
---
Apache2
=======
Alternatively, you can also use adzapper with Apache2. This has the advantage of
being IPv6 compatible. To do this, make Apache2 load mod_proxy and mod_redirect
and configure it as follows:
ProxyRequests On
RewriteEngine On
RewriteLock /var/lock/apache2/rewrite-adzapper
RewriteMap adzap prg:/usr/bin/adzapper.wrapper
<Proxy *>
Order deny,allow
Deny from all
Allow from localhost
RewriteRule ^proxy:(.*)$ proxy:${adzap:$1|$1} [L]
</Proxy>
Also, in /etc/adzapper.conf, edit the new "NO_CHANGE_VALUE" configuration
variable and set it to NULL:
NO_CHANGE_VALUE="NULL".
Polipo
======
To use Adzapper with Polipo, you will need Polipo version 0.9.99.0 or
later. Add the following line to /etc/polipo/config:
redirector = /usr/bin/adzapper.wrapper
Konqueror
=========
Just import the file /var/lib/adzapper/konqueror.txt in the AdBlocK panel.
Do not forget to clear the old list before.
Misc
====
By default, adzapper get its replacement images from
http://adzapper.sourceforge.net/zaps. If you have an http server on your
local network you can use the replacement images found in
/usr/share/doc/adzapper/examples/zaps and tell adzapper to use them by
editing /etc/adzapper.conf : Just replace the two sourceforge URLs at the
beginning of the configuration file, with your http server's URLs and uncomment
the modified lines.
If you cannot wait for Debian adzapper updates, you can update it yourself
with the script /usr/share/doc/adzapper/examples/update-zapper, but it will
overwrite the main adzapper program (/usr/bin/adzapper) !
-- Ludovic Drolez <ldrolez@debian.org>, Tue Jun 7 21:03:34 2005
|