X-Git-Url: http://www.privoxy.org/gitweb/contact.html?a=blobdiff_plain;f=doc%2Fwebserver%2Fman-page%2Fprivoxy-man-page.html;h=623226276c573cce6a0685d61009fdfa5a33d01a;hb=1d666f12f135dac7bb3540def782b94a31c93e97;hp=206f6542954a5275789303fa0469c761c8c677b6;hpb=69c8f3add321ce9df0bedcadcfc84b65b230f51f;p=privoxy.git diff --git a/doc/webserver/man-page/privoxy-man-page.html b/doc/webserver/man-page/privoxy-man-page.html index 206f6542..62322627 100644 --- a/doc/webserver/man-page/privoxy-man-page.html +++ b/doc/webserver/man-page/privoxy-man-page.html @@ -1,384 +1,202 @@ + + +
++ [--pidfile pidfile ] [--pre-chroot-nslookup hostname ] [--user + user[.group] ] [--version ] [configfile ] + + + ++
+ Privoxy may be invoked with the following command line options: + + --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. + + --config-test + Exit after loading the configuration files before binding to the + listen address. The exit code signals whether or not the + configuration files have been successfully loaded. + + If the exit code is 1, at least one of the configuration files + is invalid, if it is 0, all the configuration files have been + successfully loaded (but may still contain errors that can + currently only be detected at run time). + + This option doesn't affect the log setting, combination with + "--no-daemon" is recommended if a configured log file shouldn't + be used. + + --help Print brief usage info and exit. + + --no-daemon + Don't become a daemon, i.e. don't fork and become process + group leader, don't detach from controlling tty, and do all + logging there. + + --pidfile pidfile + On startup, write the process ID to pidfile. Delete the pidfile + on exit. Failure to create or delete the pidfile is non-fatal. + If no --pidfile option is given, no PID file will be used. + + --pre-chroot-nslookup hostname + Initialize the resolver library using hostname before + chroot'ing. On some systems this reduces the number of files + that must be copied into the chroot tree. + + --user user[.group] + After (optionally) writing the PID file, assume the user ID of + user and the GID of group, or, if the optional group was not + given, the default group of user. Exit if the privileges are not + sufficient to do so. + + + Privoxy is Free Software and licensed under the GNU GPLv2 or later. + + Privoxy is an associated project of Software in the Public Interest + (SPI). + + Helping hands and donations are welcome: + + • https://www.privoxy.org/participate + + • https://www.privoxy.org/donate + + ++
+ Browsers can either be individually configured to use Privoxy as a HTTP + proxy (recommended), or Privoxy can be combined with a packet filter to + build an intercepting proxy (see config). The default setting is for + localhost, on port 8118 (configurable in the main config file). To + set the HTTP proxy in Firefox, go through: Tools; Options; General; + Connection Settings; Manual Proxy Configuration. + + For Internet Explorer, go through: Tools; Internet Properties; + Connections; LAN Settings. + + 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. + + For other browsers, check the documentation. + + ++
+ Privoxy can be configured with the various configuration files. The + default configuration files are: config, default.filter, default.action + and default.action. user.action should be used for locally defined + exceptions to the default rules in match-all.action and 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. -Manpage of PRIVOXY - -PRIVOXY
-Section: (1)
Updated: 08 April 2002
Index -
- - -NAME
- -privoxy - Privacy Enhancing Proxy - -SYNOPSIS
- --privoxy [--help] [--version] [--no-daemon] [--pidfile pidfile] [--user user[.group]] [configfile] (UNIX) -
-
-privoxy.exe [configfile] (Windows) -
OPTIONS
- -- -Privoxy may be invoked with the following command line -options: -
- -If the configfile is not specified on the command line, -Privoxy will look for a file named -config in the current directory (except on Win32 where -it will try config.txt). If no -configfile is found, Privoxy will -fail to start. - -
- -Privoxy is a web proxy with advanced filtering -capabilities for protecting privacy, filtering web page content, managing -cookies, controlling access, and removing ads, banners, pop-ups and other -obnoxious Internet junk. Privoxy has a very -flexible configuration and can be customized to suit individual needs and -tastes. Privoxy has application for both -stand-alone systems and multi-user networks. -
- -Privoxy is based on the code of the -Internet Junkbuster (tm). -Junkbuster was originally written by JunkBusters -Corporation, and was released as free open-source software under the GNU GPL. -Stefan Waldherr made many improvements, and started the SourceForge project -to continue development. -
- -Privoxy continues the -Junkbuster tradition, but adds many -refinements, enhancements and new features. - -
- -Browsers must be individually configured to use Privoxy as -a HTTP proxy. The default setting is for localhost, on port 8118 -(configurable in the main config file). To set the HTTP proxy in Netscape -and Mozilla, go through: Edit; -Preferences; Advanced; -Proxies; Manual Proxy Configuration; -View. -
- -For Internet Explorer, go through: Tools; -Internet Properties; Connections; -LAN Settings. -
- -The Secure (SSL) Proxy should also be set to the same values, otherwise -https: URLs will not be proxied. -
- -For other browsers, check the documentation. - -
- -Privoxy can be configured with the various configuration -files. The default configuration files are: config, -default.action, and -default.filter. 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, and is subject to change as development progresses. In fact, the -configuration itself is changed and much more sophisticated. See the -user-manual for a -brief explanation of all configuration options. -
- -The actions list (ad blocks, etc) can also be configured with your -web browser at http://ijbswa.sourceforge.net/config. -Privoxy's configuration parameters can also be viewed at -the same page. In addition, Privoxy can be toggled on/off. -This is an internal page. - -
- -A brief example of what a default.action configuration -might look like: -
-
- - # Define a few useful custom aliases for later use - {{alias}} - - # Don't accept cookies - +no-cookies = +no-cookies-set +no-cookies-read - - # Do accept cookies - -no-cookies = -no-cookies-set -no-cookies-read - - # Treat these blocked URLs as images. - +imageblock = +block +image - - # Define page filters we want to use. - myfilters = +filter{html-annoyances} +filter{js-annoyances}\ - +filter{no-popups} +filter{webbugs} - - ## Default Policies (actions) ############################ - { \ - -block \ - -downgrade \ - +fast-redirects \ - myfilters \ - +no-compression \ - +hide-forwarded \ - +hide-from{block} \ - +hide-referer{forge} \ - -hide-user-agent \ - -image \ - +image-blocker{blank} \ - +no-cookies-keep \ - -no-cookies-read \ - -no-cookies-set \ - +no-popups \ - -vanilla-wafer \ - -wafer \ - } - / - - # Now set exceptions to the above defined policies ####### - - # Sites where we want persistant cookies - {-no-cookies -no-cookies-keep} - .redhat.com - .sun.com - .yahoo.com - .msdn.microsoft.com - - # This site requires cookies AND 'fast-redirects' on - {-no-cookies -no-cookies-keep -fast-redirects} - .nytimes.com - - # Add custom headers, and turn off filtering of page source - {+add-header{X-Privacy: Yes please} #-add-header{*} \ - +add-header{X-User-Tracking: No thanks!} -filter} - privacy.net - - # Block, and treat these URLs as 'images'. - {+imageblock} - .adforce.imgis.com - .ad.preferences.com/image.* - .ads.web.aol.com - .ad-adex3.flycast.com - .ad.doubleclick.net - .ln.doubleclick.net - .ad.de.doubleclick.net - /.*/count\.cgi\?.*df= - 194.221.183.22[1-7] - a196.g.akamai.net/7/196/2670/000[12]/images.gmx.net/i4/images/.*/ - - # Block any URLs that match these patterns - {+block} - /.*/(.*[-_.])?ads?[0-9]?(/|[-_.].*|\.(gif|jpe?g)) - /.*/(plain|live|rotate)[-_.]?ads?/ - /.*/(sponsor)s?[0-9]?/ - /.*/ad(server|stream|juggler)\.(cgi|pl|dll|exe) - /.*/adbanners/ - /.*/adv((er)?ts?|ertis(ing|ements?))?/ - /.*/banners?/ - /.*/popupads/ - /.*/advert[0-9]+\.jpg - /ad_images/ - /.*/ads/ - /images/.*/.*_anim\.gif - /rotations/ - /.*(ms)?backoff(ice)?.*\.(gif|jpe?g) - 195.63.104.*/(inbox|log|meld|folderlu|folderru|log(in|out)[lmr]u|) - .images.nytimes.com - .images.yahoo.com/adv/ - /.*cnnstore\.gif -- -
- -See the comments in the configuration files themselves, or the -user-manual -for explanations of the above syntax, and other Privoxy -configuration options. - -
-
- - /usr/sbin/privoxy - /etc/privoxy/config - /etc/privoxy/default.action - /etc/privoxy/advanced.action - /etc/privoxy/basic.action - /etc/privoxy/intermediate.action - /etc/privoxy/default.filter - /etc/privoxy/trust - /etc/privoxy/templates/* - /var/log/privoxy/logfile -- -
- -Various other files should be included, but may vary depending on platform -and build configuration. More documentation should be included in the local -documentation directory, though is not complete at this time. - -
- -Privoxy terminates on the SIGINT, -SIGTERM and SIGABRT signals. Log -rotation scripts may cause a re-opening of the logfile by sending a -SIGHUP to Privoxy. Note that unlike -other daemons, Privoxy does not need to be made aware of -config file changes by SIGHUP -- it will detect them -automatically. - -
- -This is a beta version of Privoxy. Not -all features are well tested. -
- -Please see the user-manual on how to contact the -developers for feature requests, reporting problems, and other questions. - -
- -Other references and sites of interest to Privoxy -users: -
- -
-http://www.privoxy.org/, -The Privoxy Home page. -
-http://sourceforge.net/projects/ijbswa, -the Project Page for Privoxy on -Sourceforge. -
-http://p.p/, access -Privoxy from your browser. Alternately, -http://config.privoxy.org -may work in some situations where the first does not. -
-http://www.junkbusters.com/ht/en/cookies.html -
-http://www.waldherr.org/junkbuster/ -
-http://privacy.net/analyze/ -
-http://www.squid-cache.org/ - -
-
- Stefan Waldherr - Andreas Oesterhelt - Jon Foster - Markus Breitenbach - Thomas Steudten - David Schmidt (OS/2, Mac OSX ports) - Gabriel L. Somlo - Hal Burgiss (docs) - Haroon Rafique - John Venvertloh - Joerg Strohmayer - Rodney Stromlund - Rodrigo Barbosa (RPM specfiles) - Sarantis Paskalis - Shamim Mohamed - Gábor Lipták - Alexander Lazic -- - -
- -Privoxy 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, which is available from the Free Software Foundation, Inc, 59 -Temple Place - Suite 330, Boston, MA 02111-1307, USA. -
- -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. -
- -
+ Privoxy terminates on the SIGINT and SIGTERM signals. Log rotation + scripts may cause a re-opening of the logfile by sending a SIGHUP to + Privoxy. Note that unlike other daemons, Privoxy does not need to be + made aware of config file changes by SIGHUP -- it will detect them + automatically. Signals other than the ones listed above aren't + explicitly handled and result in the default action defined by the + operating system. + + ++
+ Please see the User Manual on how to contact the developers, for + feature requests, reporting problems, and other questions. + + ++
+ Other references and sites of interest to Privoxy users: + + https://www.privoxy.org/, the Privoxy Home page. + + https://www.privoxy.org/faq/, the Privoxy FAQ. + + https://www.privoxy.org/developer-manual/, the Privoxy developer + manual. + + https://sourceforge.net/projects/ijbswa/, the Project Page for Privoxy + on SourceForge. + + http://config.privoxy.org/, the web-based user interface. Privoxy must + be running for this to work. Shortcut: http://p.p/ + + https://sourceforge.net/p/ijbswa/actionsfile-feedback/, to submit + ``misses'' and other configuration related suggestions to the + developers. + + ++
+ Fabian Keil, lead developer + David Schmidt + Lee Rian + Roland Rosenfeld + Ian Silvester + + ++
+ ++
+ Copyright (C) 2001-2023 by Privoxy Developers <privoxy- + devel@lists.privoxy.org> + + (at your option) any later version. + + Privoxy 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 license for details. + +Privoxy 3.0.34 05 February 2023 PRIVOXY(8) ++ +