2 File : $Source: /cvsroot/ijbswa/current/doc/source/privoxy-man-page.sgml,v $
6 ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
8 $Id: privoxy-man-page.sgml,v 1.13.2.7 2003/03/26 02:06:21 hal9 Exp $
10 Copyright (C) 2001, 2002 Privoxy Developers <developers@privoxy.org>
13 ========================================================================
14 NOTE: Please read developer-manual/documentation.html before touching
15 anything in this, or other Privoxy documentation.
16 ========================================================================
18 Doc NOTES: This is some tricky markup! There are some quirks
19 to how this markup is handled. It is not always so co-operative.
20 Please don't change the markup unless you can verify the changes
21 will improve finished output!
23 literallayout tags are particularly sensitive to where they are placed.
24 The 'replaceable' and 'command' tags are used here somewhat unconventionally,
25 since it seems to generate the proper formatting (at least for me :).
27 Create man page: 'make man'
29 Requires docbook2man (short perl script), see CVS
30 http://sources.redhat.com/docbook-tools/. Also requires openjade and SGMLSpm
33 For man page references, see:
34 http://www.linuxdoc.org/HOWTO/mini/DocBook-Install/using.html
35 http://docbook.org/tdg/en/html/ch02.html#making-refentry
38 <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN"[
39 <!entity % dummy "IGNORE">
40 <!entity p-intro SYSTEM "privoxy.sgml">
41 <!entity seealso SYSTEM "seealso.sgml">
42 <!entity copyright SYSTEM "copyright.sgml">
43 <!entity license SYSTEM "license.sgml">
44 <!entity authors SYSTEM "p-authors.sgml">
45 <!entity p-version "3.0.2">
46 <!entity p-status "stable">
47 <!entity % p-not-stable "IGNORE">
48 <!entity % p-stable "INCLUDE">
49 <!entity % p-text "IGNORE"> <!-- define we are not a text only doc -->
50 <!entity % p-authors-formal "IGNORE"> <!-- exclude additional formating -->
51 <!entity my-copy "(C)"> <!-- db2man barfs on copyright symbol -->
54 <refentry id="privoxy">
56 <date>2002-05-14</date>
59 <refentrytitle>privoxy</refentrytitle>
60 <manvolnum>1</manvolnum>
62 Privoxy &p-version;<![%p-not-stable;[ &p-status;]]>
67 <refname><application>privoxy</application></refname>
68 <refpurpose>Privacy Enhancing Proxy</refpurpose>
73 <command>privoxy</command>
74 <arg><option>--help</option></arg>
75 <arg><option>--version</option></arg>
76 <arg><option>--no-daemon</option></arg>
77 <arg><option>--pidfile </option><replaceable class="parameter">pidfile</replaceable></arg>
78 <arg><option>--user </option><replaceable class="parameter">user[.group]</replaceable></arg>
79 <arg><option>--chroot</option></arg>
80 <arg><replaceable class="parameter">configfile</replaceable></arg>
81 <command> (UNIX)</command>
85 <command>privoxy.exe</command>
86 <arg><replaceable class="parameter">configfile</replaceable></arg>
87 <command> (Windows)</command>
92 <!-- ~~~~~ New section ~~~~~ -->
93 <refsect1><title>Options</title>
95 <command>Privoxy</command> may be invoked with the following command line
104 Print brief usage info and exit.
110 <term>--version</term>
113 Print version info and exit.
119 <term>--no-daemon</term>
122 Don't become a daemon, i.e. don't fork and become process group
123 leader, don't detach from controlling tty, and do all logging there.
129 <term>--pidfile <replaceable class="parameter">pidfile</replaceable></term>
132 On startup, write the process ID to <replaceable class="parameter">pidfile</replaceable>.
133 Delete the <replaceable class="parameter">pidfile</replaceable> on exit.
134 Failure to create or delete the <replaceable class="parameter">pidfile</replaceable>
135 is non-fatal. If no <command>--pidfile</command> option is given, no PID file will be used.
141 <term>--user <replaceable class="parameter">user[.group]</replaceable></term>
144 <!-- Note: replaceable is maybe the wrong tag, but generates -->
145 <!-- correct looking man output. -->
146 After (optionally) writing the PID file, assume the user ID of
147 <replaceable class="parameter">user</replaceable> and the GID of
148 <replaceable class="parameter">group</replaceable>, or, if the optional
149 <replaceable class="parameter">group</replaceable> was not given, the default group of
150 <replaceable class="parameter">user</replaceable>. Exit if the privileges are not
156 <term>--chroot</term>
159 Before changing to the user ID given in the --user option, chroot to
160 that user's home directory, i.e. make the kernel pretend to the
161 <command>Privoxy</command> process that the directory tree starts
162 there. If set up carefully, this can limit the impact of possible
163 vulnerabilities in <command>Privoxy</command> to the files contained in
171 If the <filename>configfile</filename> is not specified on the command line,
172 <command>Privoxy</command> will look for a file named
173 <filename>config</filename> in the current directory (except on Win32 where
174 it will try <filename>config.txt</filename>). If no
175 <filename>configfile</filename> is found, <command>Privoxy</command> will
182 <!-- ~~~~~ New section ~~~~~ -->
183 <refsect1><title>Description</title>
184 <!-- Include privoxy.sgml boilerplate: -->
186 <!-- end boilerplate -->
190 <!-- ~~~~~ New section ~~~~~ -->
191 <refsect1><title>Installation and Usage</title>
193 Browsers must be individually configured to use <command>Privoxy</command> as
194 a HTTP proxy. The default setting is for localhost, on port 8118
195 (configurable in the main config file). To set the HTTP proxy in Netscape
196 and Mozilla, go through: <command>Edit</command>;
197 <command>Preferences</command>; <command>Advanced</command>;
198 <command>Proxies</command>; <command>Manual Proxy Configuration</command>;
199 <command>View</command>.
202 For Internet Explorer, go through: <command>Tools</command>;
203 <command>Internet Properties</command>; <command>Connections</command>;
204 <command>LAN Settings</command>.
207 The Secure (SSL) Proxy should also be set to the same values, otherwise
208 https: URLs will not be proxied. Note: <command>Privoxy</command> can only
209 proxy HTTP and HTTPS traffic. Do not try it with FTP or other protocols.
213 For other browsers, check the documentation.
218 <!-- ~~~~~ New section ~~~~~ -->
219 <refsect1><title>Configuration</title>
221 <command>Privoxy</command> can be configured with the various configuration
222 files. The default configuration files are: <filename>config</filename>,
223 <filename>default.filter</filename>, and
224 <filename>default.action</filename>. <filename>user.action</filename> should
225 be used for locally defined exceptions to the default rules of
226 <filename>default.action</filename> These are all well commented. On Unix
227 and Unix-like systems, these are located in
228 <filename>/etc/privoxy/</filename> by default. On Windows, OS/2 and AmigaOS,
229 these files are in the same directory as the <command>Privoxy</command>
233 The name and number of configuration files has changed from previous
234 versions<![%p-not-stable;[, and is subject to change as development
235 progresses]]>. In fact, the configuration itself is changed and much more
236 sophisticated. See the <ulink
237 url="http://www.privoxy.org/user-manual/">user-manual</ulink> for a complete
238 explanation of all configuration options and general usage, and notes for
239 upgrading from <command>Junkbuster</command> and earlier <command>Privoxy</command>
243 The actions list (ad blocks, etc) can also be configured with your
244 web browser at <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>.
245 <command>Privoxy's</command> configuration parameters can also be viewed at
246 the same page. In addition, <command>Privoxy</command> can be toggled on/off.
247 This is an internal page, and does not require Internet access.
252 <!-- ~~~~~ New section ~~~~~ -->
253 <refsect1><title>Sample Configuration</title>
255 A brief example of what a simple <filename>default.action</filename>
256 configuration might look like:
260 # Define a few useful custom aliases for later use
264 +crunch-cookies = +crunch-incoming-cookies +crunch-outgoing-cookies
265 -crunch-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies
266 +imageblock = +block +handle-as-image
268 # Fragile sites should have the minimum changes
269 fragile = -block -deanimate-gifs -fast-redirects -filter \
270 -hide-referer -prevent-cookies -kill-popups
272 ## Turn some actions on ################################
276 +deanimate-gifs{last} \
277 -downgrade-http-version \
279 +filter{html-annoyances} \
280 +filter{js-annoyances} \
281 +filter{content-cookies} \
283 +filter{banners-by-size} \
284 +hide-forwarded-for-headers \
285 +hide-from-header{block} \
286 +hide-referrer{forge} \
289 +set-image-blocker{pattern} \
291 +prevent-compression \
292 +session-cookies-only \
296 / # '/' Matches *all* URL patterns
298 # Block, and treat these URL patterns as if they were 'images'.
299 # We would expect these to be ads.
302 .a[0-9].yimg.com/(?:(?!/i/).)*$
305 # Block any URLs that match these patterns
310 /.*count(er)?\.(pl|cgi|exe|dll|asp|php[34]?)
313 # Make exceptions for these harmless ones that would be
314 # caught by our +block patterns just above.
323 Then for a <filename>user.action</filename>, we would put local,
324 narrowly defined exceptions:
328 # Re-define aliases as needed here
332 -crunch-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies
334 # Set personal exceptions to the policies in default.action #######
336 # Sites where we want persistant cookies, so allow *all* cookies
337 {-crunch-cookies -session-cookies-only}
342 # This site breaks easily.
343 {-block -fast-redirects}
349 See the comments in the configuration files themselves, or the
350 <citetitle>user-manual</citetitle>
351 for explanations of the above syntax, and other <command>Privoxy</command>
352 configuration options.
358 <!-- ~~~~~ New section ~~~~~ -->
359 <refsect1><title>Files</title>
360 <!-- this is a cheesy way to do this, but WTF. -->
362 <filename>/usr/sbin/privoxy</filename>
363 <filename>/etc/privoxy/config</filename>
364 <filename>/etc/privoxy/default.action</filename>
365 <filename>/etc/privoxy/standard.action</filename>
366 <filename>/etc/privoxy/user.action</filename>
367 <filename>/etc/privoxy/default.filter</filename>
368 <filename>/etc/privoxy/trust</filename>
369 <filename>/etc/privoxy/templates/*</filename>
370 <filename>/var/log/privoxy/logfile</filename>
374 Various other files should be included, but may vary depending on platform
375 and build configuration. More documentation should be included in the local
376 documentation directory.
382 <!-- ~~~~~ New section ~~~~~ -->
383 <refsect1><title>Signals</title>
385 <!-- command tag is used here to get proper looking format -->
386 <command>Privoxy</command> terminates on the <command>SIGINT</command>,
387 <command>SIGTERM</command> and <command>SIGABRT</command> signals. Log
388 rotation scripts may cause a re-opening of the logfile by sending a
389 <command>SIGHUP</command> to <command>Privoxy</command>. Note that unlike
390 other daemons, <command>Privoxy</command> does not need to be made aware of
391 config file changes by <command>SIGHUP</command> -- it will detect them
397 <!-- ~~~~~ New section ~~~~~ -->
398 <refsect1><title>Notes</title>
401 This is a &p-status; version of <command>Privoxy</command>. Not
402 all features are well tested.
405 Please see the <citetitle>User Manual</citetitle> on how to contact the
406 developers for feature requests, reporting problems, and other questions.
411 <!-- ~~~~~ New section ~~~~~ -->
412 <refsect1><title>See Also</title>
413 <!-- Include seealso.sgml boilerplate: -->
415 <!-- end boilerplate -->
418 <!-- ~~~~~ New section ~~~~~ -->
419 <refsect1><title>Development Team</title>
420 <!-- Include p-authors.sgml boilerplate: -->
422 <!-- end boilerplate -->
425 <!-- ~~~~~ New section ~~~~~ -->
426 <refsect1><title>Copyright and License</title>
428 <refsect2><title>Copyright</title>
429 <!-- Include copyright.sgml boilerplate: -->
431 <!-- end boilerplate -->
434 <refsect2><title>License</title>
435 <!-- Include license.sgml boilerplate: -->
437 <!-- end boilerplate -->