X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fsource%2Fuser-manual.sgml;h=b5e86ba5f619669c70293e3334b5317432fba6ce;hb=d7900699eb8ddd647aa6ac52c2a048ba3c130113;hp=d599631e3ddf95a513f8b9c7926b7f3fe12be4b2;hpb=764090bd9b33279e6ffb040521b67620cdc33a70;p=privoxy.git diff --git a/doc/source/user-manual.sgml b/doc/source/user-manual.sgml index d599631e..b5e86ba5 100644 --- a/doc/source/user-manual.sgml +++ b/doc/source/user-manual.sgml @@ -24,7 +24,7 @@ This file belongs into ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/ - $Id: user-manual.sgml,v 1.78 2002/04/17 18:04:16 oes Exp $ + $Id: user-manual.sgml,v 1.83 2002/04/18 18:21:12 oes Exp $ Written by and Copyright (C) 2001 the SourceForge Privoxy team. http://www.privoxy.org/ @@ -45,7 +45,7 @@ Privoxy User Manual -$Id: user-manual.sgml,v 1.78 2002/04/17 18:04:16 oes Exp $ +$Id: user-manual.sgml,v 1.83 2002/04/18 18:21:12 oes Exp $ @@ -100,7 +100,6 @@ Introduction - This documentation is included with the current &p-status; version of Privoxy, v.&p-version;Privoxy provides new features: - @@ -145,12 +143,14 @@ Installation + Privoxy is available both in convenient pre-compiled packages for a wide range of operating systems, and as raw source code. For most users, we recommend using the packages, which can be downloaded from our Privoxy Project Page. + If you like to live on the bleeding edge and are not afraid of using possibly unstable development versions, you can check out the up-to-the-minute @@ -166,36 +166,46 @@ Binary Packages + + + Note: If you have a previous Junkbuster or + Privoxy installation on your system, you + will either need to remove it, or that might be done by the setup + procedure. (See below for your platform). + + - Binary packages can be downloaded from our Privoxy Project Page. + In any case be sure to backup your old configuration + if it is valuable to you. In that case, also see the + note to upgraders. - How to install them depends on your operating system: + How to install the binary packages depends on your operating system: -Redhat and SuSE RPMs +Red Hat and SuSE RPMs RPMs can be installed with rpm -Uvh <name-of-rpm.rpm>, - and will use /etc/privoxy for configuration files. + and will use /etc/privoxy for the location + of configuration files. Note that if you have a Junkbuster RPM installed on your system, you need to remove it first, because the packages conflict. + Otherwise, RPM will try to remove Junkbuster + automatically, before installing Privoxy. + future reference. -Solaris, NetBSD, HP-UX - +Debian - Create a new directory, cd to it, then unzip and - untar the archive. For the most part, you'll have to figure out where - things go. FIXME. + FIXME. @@ -208,12 +218,29 @@ + +Solaris, NetBSD, FreeBSD, HP-UX + + + Create a new directory, cd to it, then unzip and + untar the archive. For the most part, you'll have to figure out where + things go. FIXME. + + + OS/2 - Just double-click the WarpIN self-installing archive, which will guide - you through the installation process. A shadow of the + First, make sure that no previous installations of + Junkbuster and / or + Privoxy are left on your + system. + + + + Then, just double-click the WarpIN self-installing archive, which will + guide you through the installation process. A shadow of the Privoxy executable will be placed in your startup folder so it will start automatically whenever OS/2 starts. @@ -225,7 +252,7 @@ -Debian +Max OSX FIXME. @@ -245,13 +272,6 @@ &buildsource; - - - For more detailed instructions, on how to build Redhat and SuSE RPMs, - Windows self-extracting installers etc, and for building from CVS sources, - please consult the developer - manual. - @@ -389,7 +409,7 @@ - An init script is provided for SuSE and Redhat. + An init script is provided for SuSE and Red Hat. @@ -397,7 +417,7 @@ - For RedHat: /etc/rc.d/init.d/privoxy start + For Red Hat: /etc/rc.d/init.d/privoxy start @@ -775,7 +795,7 @@ Please choose from the following options: The main config file controls all aspects of Privoxy's - operation that are not location dependent (i.e. they apply to all URLs, no matter + operation that are not location dependent (i.e. they apply universally, no matter where you may be surfing). @@ -1022,7 +1042,7 @@ Please choose from the following options: Your logfile will grow indefinitely, and you will probably want to periodically remove it. On Unix systems, you can do this with a cron job - (see man cron). For Redhat, a logrotate + (see man cron). For Red Hat, a logrotate script has been included. @@ -2088,7 +2108,7 @@ Please choose from the following options: Now, your users can set their browser's proxy to use either host-a or host-b and be able to browse the internal content - on both isp-a or isp-b. + of both isp-a and isp-b. @@ -2336,7 +2356,7 @@ Removed references to Win32. HB 09/23/01 Note that some actions like cookie suppression or script disabling may render some sites unusable, which rely on these techniques to work properly. - Finding the right mix of actions is not easy and a matter of personal + Finding the right mix of actions is not easy and certainly a matter of personal taste. In general, it can be said that the more aggressive your default settings (in the top section of the actions file) are, the more exceptions for trusted sites you will have to @@ -2404,26 +2424,27 @@ Removed references to Win32. HB 09/23/01 Patterns - Generally, a pattern has the form <domain>/<path>, where both the - <domain> and <path> part are optional. If you only specify a - domain part, the / can be left out: + Generally, a pattern has the form <domain>/<path>, + where both the <domain> and <path> + are optional. (This is why the pattern / matches all URLs). - www.example.com + www.example.com/ - is a domain only pattern and will match any request to www.example.com, + is a domain-only pattern and will match any request to www.example.com, regardless of which document on that server is requested. - www.example.com/ + www.example.com - means exactly the same. + means exactly the same. For domain-only patterns, the trailing / may + be omitted. @@ -2562,7 +2583,7 @@ Removed references to Win32. HB 09/23/01 - Note that the pattern is automatically left-anchored at the /, + Note that the path pattern is automatically left-anchored at the /, i.e. it matches as if it would start with a ^. @@ -2822,12 +2843,17 @@ Removed references to Win32. HB 09/23/01 - no-popups: Kill all popups in JS and HTML + content-cookies: Kill cookies that come in the HTML or JS content - frameset-borders: Give frames a border + popups: Kill all popups in JS and HTML + + + + + frameset-borders: Give frames a border and make them resizable @@ -2837,7 +2863,7 @@ Removed references to Win32. HB 09/23/01 - no-refresh: Automatic refresh sucks on auto-dialup lines + refresh-tags: Kill automatic refresh tags (for dial-on-demand setups) @@ -2847,12 +2873,17 @@ Removed references to Win32. HB 09/23/01 - nimda: Remove (virus) Nimda code. + nimda: Remove Nimda (virus) code. + + + + + banners-by-size: Kill banners by size (very efficient!) - banners-by-size: Kill banners by size + shockwave-flash: Kill embedded Shockwave Flash objects @@ -2862,6 +2893,7 @@ Removed references to Win32. HB 09/23/01 + Note: Filtering requires buffering the page content, which may appear to slow down page rendering since nothing is displayed until all content has passed @@ -4395,6 +4427,21 @@ Requests Temple Place - Suite 330, Boston, MA 02111-1307, USA. $Log: user-manual.sgml,v $ + Revision 1.83 2002/04/18 18:21:12 oes + Added RPM install detail + + Revision 1.82 2002/04/18 12:04:50 oes + Cosmetics + + Revision 1.81 2002/04/18 11:50:24 oes + Extended Install section - needs fixing by packagers + + Revision 1.80 2002/04/18 10:45:19 oes + Moved text to buildsource.sgml, renamed some filters, details + + Revision 1.79 2002/04/18 03:18:06 hal9 + Spellcheck, and minor touchups. + Revision 1.78 2002/04/17 18:04:16 oes Proofreading part 2