X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fman-page%2Fprivoxy-man-page.html;h=44c37ef59bcb6c7b72eb3f15fca16f0ee74aa181;hp=71e518014fc0f0fcf9118db355502830fd04ce7d;hb=322389db65561716cdc35949eea8ae911f8a0aa8;hpb=72081f829de368392d04076728f8c991178c0080 diff --git a/doc/webserver/man-page/privoxy-man-page.html b/doc/webserver/man-page/privoxy-man-page.html index 71e51801..44c37ef5 100644 --- a/doc/webserver/man-page/privoxy-man-page.html +++ b/doc/webserver/man-page/privoxy-man-page.html @@ -1,8 +1,9 @@ -Manpage of PRIVOXY + +Man page of PRIVOXY

PRIVOXY

-Section: (1)
Updated: 25 March 2003
Index +Section: (1)
Updated: 20 February 2009
Index
  @@ -13,10 +14,7 @@ privoxy - Privacy Enhancing Proxy

SYNOPSIS

-privoxy [--help ] [--version ] [--no-daemon ] [--pidfile pidfile ] [--user user[.group] ] [--chroot ] [configfile ] (UNIX) -

-

-privoxy.exe [configfile ] (Windows) +privoxy [--help ] [--version ] [--no-daemon ] [--pidfile pidfile ] [--user user[.group] ] [--chroot ] [--pre-chroot-nslookup hostname ] [configfile ]

 

OPTIONS

@@ -52,13 +50,16 @@ that user's home directory, i.e. make the kernel pretend to the there. If set up carefully, this can limit the impact of possible vulnerabilities in Privoxy to the files contained in that hierarchy. +
--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.

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 +config in the current directory. If no configfile is found, Privoxy will fail to start.   @@ -66,29 +67,33 @@ 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 a non-caching +web proxy +with advanced filtering capabilities for enhancing privacy, +modifying web page data, managing HTTP +cookies, +controlling access, and removing ads, banners, pop-ups and other obnoxious +Internet junk. Privoxy has a 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 Internet -Junkbuster (tm). +Privoxy is based on Internet Junkbuster (tm).  

INSTALLATION AND USAGE

-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. +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; @@ -99,6 +104,8 @@ For Internet Explorer, go through: Tools; 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. @@ -109,131 +116,36 @@ For other browsers, check the documentation. Privoxy can be configured with the various configuration files. The default configuration files are: config, -default.filter, and +default.filter, default.action 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 -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. +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.

-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. +Privoxy uses the concept of actions +in order to manipulate the data stream between the browser and remote sites. +There are various actions available with specific functions for such things +as blocking web sites, managing cookies, etc. These actions can be invoked +individually or combined, and used against individual URLs, or groups of URLs +that can be defined using wildcards and regular expressions. The result is +that the user has greatly enhanced control and freedom.

The actions list (ad blocks, etc) can also be configured with your -web browser at http://config.privoxy.org/. +web browser at http://config.privoxy.org/ +(assuming the configuration allows it). 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, and does not require Internet access. -  -

SAMPLE CONFIGURATION

- -

- -A brief example of what a simple default.action -configuration might look like: -

-

- # Define a few useful custom aliases for later use
- {{alias}}
-
- # Useful aliases
- +crunch-cookies = +crunch-incoming-cookies +crunch-outgoing-cookies
- -crunch-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies
- +imageblock      = +block +handle-as-image
-
- # Fragile sites should have the minimum changes
- fragile     = -block -deanimate-gifs -fast-redirects -filter \
-               -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
- 
- # Block, and treat these URL patterns as if they were 'images'.
- # We would expect these to be ads.
- {+imageblock}
-  .ad.doubleclick.net
-  .a[0-9].yimg.com/(?:(?!/i/).)*$
-  ad.*.doubleclick.net
-
- # Block any URLs that match these patterns
- {+block}
-  ad*.
-  .*ads.
-  banner?.
-  /.*count(er)?\.(pl|cgi|exe|dll|asp|php[34]?)
-  .hitbox.com 
-
- # Make exceptions for these harmless ones that would be 
- # caught by our +block patterns just above.
- {-block}
-  adsl.
-  advice.
-  .*downloads.
-
- -

- -Then for a user.action, we would put local, -narrowly defined exceptions: -

-

- # Re-define aliases as needed here
- {{alias}}
-
- # Useful aliases
- -crunch-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies
- 
- # Set personal exceptions to the policies in default.action #######
-
- # Sites where we want persistant cookies, so allow *all* cookies
- {-crunch-cookies -session-cookies-only}
-  .redhat.com
-  .sun.com
-  .msdn.microsoft.com
- 
- # This site breaks easily.
- {-block -fast-redirects}
-  .forbes.com
-
-

-See the comments in the configuration files themselves, or the -user-manual -for explanations of the above syntax, and other Privoxy -configuration options. -  +See the User Manual for a detailed +explanation of installation, general usage, all configuration options, new +features and notes on upgrading. + 

FILES

@@ -241,10 +153,11 @@ configuration options. /usr/sbin/privoxy /etc/privoxy/config + /etc/privoxy/match-all.action /etc/privoxy/default.action - /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 @@ -253,9 +166,9 @@ configuration options.

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. -  + 

SIGNALS

@@ -267,14 +180,14 @@ rotation scripts may cause a re-opening of the logfile by sending a other daemons, Privoxy does not need to be made aware of config file changes by SIGHUP -- it will detect them automatically. -  + 

NOTES

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. + 

SEE ALSO

@@ -290,7 +203,7 @@ the Privoxy Home page. http://www.privoxy.org/faq/, the Privoxy FAQ.

-http://sourceforge.net/projects/ijbswa/, +https://sourceforge.net/projects/ijbswa/, the Project Page for Privoxy on SourceForge.

@@ -298,97 +211,61 @@ SourceForge. the web-based user interface. Privoxy must be running for this to work. Shortcut: http://p.p/

-http://www.privoxy.org/actions/, to submit ``misses'' to the developers. -

-http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/ijbswa/contrib/, cool -and fun ideas from Privoxy users. -

-http://www.junkbusters.com/ht/en/cookies.html, -an explanation how cookies are used to track web users. -

-http://www.junkbusters.com/ijb.html, -the original Internet Junkbuster. -

-http://www.waldherr.org/junkbuster/, -Stefan Waldherr's version of Junkbuster, from which Privoxy was -derived. -

-http://privacy.net/analyze/, a useful site -to check what information about you is leaked while you browse the web. -

-http://www.squid-cache.org/, a very popular -caching proxy, which is often used together with Privoxy. +https://sourceforge.net/tracker/?group_id=11118&atid=460288, to submit ``misses'' and other +configuration related suggestions to the developers.

http://www.privoxy.org/developer-manual/, the Privoxy developer manual. -  + 

DEVELOPMENT TEAM

- Hal Burgiss (docs)
- Jon Foster
- Andreas Oesterhelt
- David Schmidt (OS/2, Mac OSX ports)
-
- Johny Agotnes 
- Rodrigo Barbosa (RPM specfiles)
- Moritz Barsnick
- Mattes Dolak 
- Karsten Hopp (Red Hat)
- Alexander Lazic
- Daniel Leite
- Gábor Lipták
- Adam Lock (Win32)
- Guy Laroche
- Haroon Rafique
- Roland Rosenfeld (Debian)
- Georg Sauthoff (Gentoo)
- Thomas Steudten
- Joerg Strohmayer (Amiga)
- Rodney Stromlund
- Sviatoslav Sviridov
- Sarantis Paskalis
- Stefan Waldherr
+ Fabian Keil, lead developer
+ David Schmidt, developer
+
+ Hal Burgiss
+ Mark Miller
+ Gerry Murphy
+ Lee Rian
+ Roland Rosenfeld
+ Jörg Strohmayer
 
-  + 

COPYRIGHT AND LICENSE

-  + 

COPYRIGHT

-Copyright (C) 2001 - 2003 by Privoxy Developers <developers@privoxy.org> +Copyright (C) 2001-2009 by Privoxy Developers <ijbswa-developers@lists.sourceforge.net>

Some source code is based on code Copyright (C) 1997 by Anonymous Coders and Junkbusters, Inc. and licensed under the GNU General Public License. -  + 

LICENSE

Privoxy is free software; you can redistribute it and/or modify it under the terms of the -GNU General Public -License, version 2, as published by the Free Software Foundation. +GNU General Public License, version 2, +as published by the Free Software Foundation.

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. +FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for details.

-You should have received a copy of the GNU General Public License +You should have received a copy of the GNU GPL along with this program; if not, write to the Free Software -Foundation, Inc. 59 Temple Place - Suite 330 -Boston, MA 02111-1307 +Foundation, Inc. 51 Franklin Street, Fifth Floor +Boston, MA 02110-1301 USA

@@ -401,22 +278,21 @@ USA

DESCRIPTION
INSTALLATION AND USAGE
CONFIGURATION
-
SAMPLE CONFIGURATION
-
FILES
-
SIGNALS
-
NOTES
-
SEE ALSO
-
DEVELOPMENT TEAM
-
COPYRIGHT AND LICENSE
+
FILES
+
SIGNALS
+
NOTES
+
SEE ALSO
+
DEVELOPMENT TEAM
+
COPYRIGHT AND LICENSE
-
COPYRIGHT
-
LICENSE
+
COPYRIGHT
+
LICENSE

This document was created by man2html, using the manual pages.
-Time: 02:05:48 GMT, March 26, 2003 +Time: 00:06:06 GMT, February 21, 2009