X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fsource%2Fprivoxy-man-page.sgml;h=445a7159e737b2edc0cafcdbd56ae080eda58322;hb=03e14880e78a4d03caa7fb4c809e48dbaef04a37;hp=faabc56dadbbf03c70fad9dd452876d50a91e3c2;hpb=4f6763ba9c8e92e60879832d264b81f10095117b;p=privoxy.git diff --git a/doc/source/privoxy-man-page.sgml b/doc/source/privoxy-man-page.sgml index faabc56d..445a7159 100644 --- a/doc/source/privoxy-man-page.sgml +++ b/doc/source/privoxy-man-page.sgml @@ -5,9 +5,9 @@ This file belongs into ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/ - $Id: privoxy-man-page.sgml,v 2.3 2002/09/05 05:45:30 hal9 Exp $ + $Id: privoxy-man-page.sgml,v 2.6 2006/08/26 02:37:27 hal9 Exp $ - Copyright (C) 2001, 2002 Privoxy Developers + Copyright (C) 2001-2006 Privoxy Developers See LICENSE. ======================================================================== @@ -24,6 +24,12 @@ The 'replaceable' and 'command' tags are used here somewhat unconventionally, since it seems to generate the proper formatting (at least for me :). + Create man page: 'make man' + + Requires docbook2man (short perl script), see CVS + http://sources.redhat.com/docbook-tools/. Also requires openjade and SGMLSpm + perl module. + For man page references, see: http://www.linuxdoc.org/HOWTO/mini/DocBook-Install/using.html http://docbook.org/tdg/en/html/ch02.html#making-refentry @@ -36,12 +42,10 @@ - - - + + + - - @@ -49,7 +53,7 @@ - 2002-05-14 + 2006-08-24 privoxy @@ -72,6 +76,7 @@ pidfile user[.group] + configfile  (UNIX) @@ -147,8 +152,21 @@ + + --chroot + + + Before changing to the user ID given in the --user option, chroot to + that user's home directory, i.e. make the kernel pretend to the + Privoxy process that the directory tree starts + there. If set up carefully, this can limit the impact of possible + vulnerabilities in Privoxy to the files contained in + that hierarchy. + + + - + If the configfile is not specified on the command line, Privoxy will look for a file named @@ -189,6 +207,8 @@ The Secure (SSL) Proxy should also be set to the same values, otherwise https: URLs will not be proxied. Note: Privoxy can only proxy HTTP and HTTPS traffic. Do not try it with FTP or other protocols. + HTTPS presents some limitations, and not all features will work with HTTPS + connections. @@ -205,21 +225,18 @@ default.filter, and default.action. user.action should be used for locally defined exceptions to the default rules of - default.action These are all well commented. On Unix + default.action, and user.filter for + locally defined filters. These are well commented. On Unix and Unix-like systems, these are located in /etc/privoxy/ by default. On Windows, OS/2 and AmigaOS, these files are in the same directory as the Privoxy executable. - The name and number of configuration files has changed from previous - versions. In fact, the configuration itself is changed and much more - sophisticated. See the user-manual for a complete - explanation of all configuration options and general usage, and notes for - upgrading from Junkbuster and earlier Privoxy - versions. + explanation of installation, general usage, all configuration options, new + features and notes on upgrading. The actions list (ad blocks, etc) can also be configured with your @@ -252,30 +269,68 @@ -hide-referer -prevent-cookies -kill-popups ## Turn some actions on ################################ - { \ - -add-header \ - -block \ - +deanimate-gifs{last} \ - -downgrade-http-version \ - -fast-redirects \ - +filter{html-annoyances} \ - +filter{js-annoyances} \ - +filter{content-cookies} \ - +filter{webbugs} \ - +filter{banners-by-size} \ - +hide-forwarded-for-headers \ - +hide-from-header{block} \ - +hide-referrer{forge} \ - -hide-user-agent \ - -handle-as-image \ - +set-image-blocker{pattern} \ - -limit-connect \ - +prevent-compression \ - +session-cookies-only \ - -crunch-cookies \ - -kill-popups \ - } - / # '/' Matches *all* URL patterns + ## NOTE: Actions are off by default, unless explictily turned on + ## otherwise with the '+' operator. + +{ \ +-add-header \ +-block \ +-content-type-overwrite \ +-crunch-client-header \ +-crunch-if-none-match \ +-crunch-outgoing-cookies \ +-crunch-incoming-cookies \ +-crunch-server-header \ ++deanimate-gifs{last} \ +-downgrade-http-version \ +-fast-redirects \ ++filter{js-annoyances} \ +-filter{js-events} \ ++filter{html-annoyances} \ +-filter{content-cookies} \ ++filter{refresh-tags} \ ++filter{unsolicited-popups} \ +-filter{all-popups} \ ++filter{img-reorder} \ ++filter{banners-by-size} \ +-filter{banners-by-link} \ ++filter{webbugs} \ +-filter{tiny-textforms} \ ++filter{jumping-windows} \ +-filter{frameset-borders} \ +-filter{demoronizer} \ +-filter{shockwave-flash} \ +-filter{quicktime-kioskmode} \ +-filter{fun} \ +-filter{crude-parental} \ ++filter{ie-exploits} \ +-filter{site-specifics} \ +-filter-client-headers \ +-filter-server-headers \ +-force-text-mode \ +-handle-as-empty-document +-handle-as-image \ +-hide-accept-language \ +-hide-content-disposition \ +-hide-if-modified-since \ ++hide-forwarded-for-headers \ ++hide-from-header{block} \ ++hide-referrer{forge} \ +-hide-user-agent \ +-inspect-jpegs \ +-kill-popups \ +-limit-connect \ +-overwrite-last-modified \ +-redirect \ ++prevent-compression \ +-send-vanilla-wafer \ +-send-wafer \ ++session-cookies-only \ ++set-image-blocker{pattern} \ +-treat-forbidden-connects-like-blocks \ +} +/ # '/' Match *all* URL patterns + # Block, and treat these URL patterns as if they were 'images'. # We would expect these to be ads. @@ -347,6 +402,7 @@ /etc/privoxy/standard.action /etc/privoxy/user.action /etc/privoxy/default.filter + /etc/privoxy/user.filter /etc/privoxy/trust /etc/privoxy/templates/* /var/log/privoxy/logfile @@ -354,7 +410,7 @@ Various other files should be included, but may vary depending on platform - and build configuration. More documentation should be included in the local + and build configuration. Additional documentation should be included in the local documentation directory. @@ -385,7 +441,7 @@ ]]> Please see the User Manual on how to contact the - developers for feature requests, reporting problems, and other questions. + developers, for feature requests, reporting problems, and other questions.