From d09495686ceb54f830dfecefcdfdde1061cc8f33 Mon Sep 17 00:00:00 2001 From: hal9 Date: Tue, 14 Nov 2006 01:57:47 +0000 Subject: [PATCH] Dump all docs prior to 3.0.6 release. Various minor changes to faq and user manual. --- doc/source/announce.sgml | 24 +-- doc/source/authors.sgml | 10 +- doc/source/buildsource.sgml | 58 ++++---- doc/source/config.sgml | 8 +- doc/source/contacting.sgml | 4 +- doc/source/developer-manual.sgml | 19 ++- doc/source/faq.sgml | 193 +++++++++++++++++------- doc/source/install.sgml | 10 +- doc/source/newfeatures.sgml | 7 +- doc/source/p-authors.sgml | 16 +- doc/source/privoxy-man-page.sgml | 8 +- doc/source/readme.sgml | 30 ++-- doc/source/user-manual.sgml | 248 ++++++++++++++++++++----------- 13 files changed, 406 insertions(+), 229 deletions(-) diff --git a/doc/source/announce.sgml b/doc/source/announce.sgml index b757e89e..928efb60 100644 --- a/doc/source/announce.sgml +++ b/doc/source/announce.sgml @@ -5,11 +5,10 @@ - - - - - + + + + @@ -20,7 +19,7 @@ Purpose : Announcement text - $Id: announce.sgml,v 2.3 2006/07/18 14:48:50 david__schmidt Exp $ + $Id: announce.sgml,v 2.4 2006/09/22 01:27:55 hal9 Exp $ Copyright (C) 2001-2006 Privoxy Developers http://www.privoxy.org See LICENSE. @@ -60,16 +59,19 @@ v.&p-version; + + This is a significant release with many new features, including a number of + new actions, and as well as many enhancements and numerous bugs done away + with. See + http://www.privoxy.org/user-manual/whatsnew.html + for details. + + &p-intro; - -New in this release - &newstuff; - - &supported; diff --git a/doc/source/authors.sgml b/doc/source/authors.sgml index 4f20931b..e6c65cb8 100644 --- a/doc/source/authors.sgml +++ b/doc/source/authors.sgml @@ -3,7 +3,7 @@ Purpose : AUTHORS file for Privoxy - $Id: authors.sgml,v 2.3 2006/07/18 14:48:50 david__schmidt Exp $ + $Id: authors.sgml,v 2.4 2006/09/22 01:27:55 hal9 Exp $ Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org @@ -26,10 +26,10 @@ - - - - + + + + ]> diff --git a/doc/source/buildsource.sgml b/doc/source/buildsource.sgml index 1db9dce9..e128d04d 100644 --- a/doc/source/buildsource.sgml +++ b/doc/source/buildsource.sgml @@ -3,7 +3,7 @@ Purpose : Entity included in other project documents. - $Id: buildsource.sgml,v 2.10 2006/10/14 23:03:56 hal9 Exp $ + $Id: buildsource.sgml,v 2.11 2006/10/14 23:06:48 hal9 Exp $ Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org See LICENSE. @@ -49,7 +49,7 @@ For retrieving the current CVS sources, you'll need a CVS client installed. - Note that sources from CVS are typicially development quality, and may not be + Note that sources from CVS are typically development quality, and may not be stable, or well tested. To download CVS source, check the Sourceforge documentation, which might give commands like: @@ -76,9 +76,12 @@ It is also strongly recommended to not run Privoxy - as root, and instead it is suggested to create a privoxy user - and group for this purpose. See your local documentation for the correct - command line to do this. + as root. You should configure/install/run Privoxy as + an unprivileged user, preferably by creating a privoxy user + and group just for this purpose. See your local documentation for the correct + command line to do add new users and groups (something like + adduser, but the command syntax may vary from platform + to platform). @@ -111,13 +114,13 @@ autoconf ./configure # (--help to see options) make # (the make from GNU, sometimes called gmake) - su + su # Possibly required make -n install # (to see where all the files will go) make -s install # (to really install, -s to silence output) - If you have GNU make, you can have the first four steps + Using GNU make, you can have the first four steps automatically done for you by just typing: @@ -133,8 +136,8 @@ To build an executable with security enhanced features so that - users cannot easily bypass the proxy (e.g. go there anyway), or - change their own configurations, configure like this: + users cannot easily bypass the proxy (e.g. Go There Anyway), or + alter their own configurations, configure like this: @@ -158,8 +161,8 @@ Then build as above. --with-group options for setting user and group ownership of the configuration files (which need to be writable by the daemon). The specified user must already exist. When starting - Privoxy, it should be run as this same user to - insure write access to configuration and log files. + Privoxy, it must be run as this same user to + insure write access to configuration and log files! @@ -176,9 +179,10 @@ Then build as above. The default installation path for make install is /usr/local. This may of course be customized with the various ./configure path options. If you are doing - a root install to anywhere else besides /usr/local, be + an install to anywhere besides /usr/local, be sure to set the appropriate paths with the correct configure options - (./configure --help). + (./configure --help). Non-privileged users must of course + have write access permissions to wherever the target installation is going. @@ -192,10 +196,10 @@ Then build as above. - If installing to /usr/local, the docs will go by default - to $prefix/share/doc. But if this directory doesn't - exist, it will then try $prefix/doc and install there before - creating a new $prefix/share/doc just for + If installing to /usr/local, the documentation will go + by default to $prefix/share/doc. But if this directory + doesn't exist, it will then try $prefix/doc and install + there before creating a new $prefix/share/doc just for Privoxy. @@ -209,8 +213,8 @@ Then build as above. make install will attempt to set the correct values - in config (main configuration file). You may want - to check this to make sure all values are correct. If appropriate, + in config (main configuration file). You should + check this to make sure all values are correct. If appropriate, an init script will be installed, but it is up to the user to determine how and where to start Privoxy. The init script should be checked for correct paths and values, if anything other than @@ -218,14 +222,16 @@ Then build as above. - If install finds previous versions of any local configuration files, these - will not be overwritten, and the new ones will be installed with a + If install finds previous versions of local configuration files, most of + these will not be overwritten, and the new ones will be installed with a new extension. default.action, default.filter, and - standard.action will be overwritten. You will then need to manually update - the other installed configuration files as needed. All template files will be - overwritten. If you have customized, local templates, you should save these - first. If a previous version of Privoxy is - already running, you will have to restart it manually. + standard.action will be overwritten. You will then need + to manually update the other installed configuration files as needed. All + template files will be overwritten. If you have customized, local templates, + you should save these first, and in fact it is wise to always save any + important configuration files just in case. If a previous + version of Privoxy is already running, you will + have to restart it manually. diff --git a/doc/source/config.sgml b/doc/source/config.sgml index a848b849..318db0ea 100644 --- a/doc/source/config.sgml +++ b/doc/source/config.sgml @@ -1,9 +1,9 @@ - - - + + + ]> @@ -12,7 +12,7 @@ Purpose : config file generation - $Id: config.sgml,v 2.3 2006/07/18 14:48:50 david__schmidt Exp $ + $Id: config.sgml,v 2.4 2006/09/22 01:27:55 hal9 Exp $ Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org See LICENSE. diff --git a/doc/source/contacting.sgml b/doc/source/contacting.sgml index e1bbdec5..99192fc3 100644 --- a/doc/source/contacting.sgml +++ b/doc/source/contacting.sgml @@ -3,7 +3,7 @@ Purpose : Entity included in other project documents. - $Id: contacting.sgml,v 2.8 2006/09/22 01:27:55 hal9 Exp $ + $Id: contacting.sgml,v 2.9 2006/09/22 13:30:57 fabiankeil Exp $ Copyright (C) 2001 - 2006 Privoxy Developers http://privoxy.org See LICENSE. @@ -142,7 +142,7 @@ Please be sure to provide the following information: The operating system and versions you run Privoxy on, (e.g. Windows - XP SP2), if you are using some kind of Unix flavour, + XP SP2), if you are using a Unix flavor, sending the output of uname -a should do. diff --git a/doc/source/developer-manual.sgml b/doc/source/developer-manual.sgml index 362b5f5b..c453381a 100644 --- a/doc/source/developer-manual.sgml +++ b/doc/source/developer-manual.sgml @@ -8,10 +8,10 @@ - - - - + + + + @@ -23,7 +23,7 @@ This file belongs into ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/ - $Id: developer-manual.sgml,v 2.10 2006/09/22 01:27:55 hal9 Exp $ + $Id: developer-manual.sgml,v 2.11 2006/09/26 02:36:29 hal9 Exp $ Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org See LICENSE. @@ -50,7 +50,7 @@ - $Id: developer-manual.sgml,v 2.10 2006/09/22 01:27:55 hal9 Exp $ + $Id: developer-manual.sgml,v 2.11 2006/09/26 02:36:29 hal9 Exp $ ource$ @@ -1893,7 +1893,7 @@ const char FILENAME_h_rcs[] = FILENAME_H_VERSION; #ifndef _FILENAME_H #define _FILENAME_H -#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 2.10 2006/09/22 01:27:55 hal9 Exp $" +#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 2.11 2006/09/26 02:36:29 hal9 Exp $" /********************************************************************* * * File : $Source$ @@ -3025,6 +3025,9 @@ at sourceforge. Three simple steps: Temple Place - Suite 330, Boston, MA 02111-1307, USA. $Log: developer-manual.sgml,v $ + Revision 2.11 2006/09/26 02:36:29 hal9 + Fix broken link per bug tracker. + Revision 2.10 2006/09/22 01:27:55 hal9 Final commit of probably various minor changes here and there. Unless something changes this should be ready for pending release. diff --git a/doc/source/faq.sgml b/doc/source/faq.sgml index 007f6139..9857eb32 100644 --- a/doc/source/faq.sgml +++ b/doc/source/faq.sgml @@ -8,8 +8,8 @@ - - + + @@ -26,7 +26,7 @@ This file belongs into ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/ - $Id: faq.sgml,v 2.22 2006/10/14 20:33:10 hal9 Exp $ + $Id: faq.sgml,v 2.23 2006/10/21 22:19:52 hal9 Exp $ Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org See LICENSE. @@ -77,7 +77,7 @@ -$Id: faq.sgml,v 2.22 2006/10/14 20:33:10 hal9 Exp $ +$Id: faq.sgml,v 2.23 2006/10/21 22:19:52 hal9 Exp $ @@ -16,7 +16,7 @@ Purpose : INSTALL file for Privoxy - $Id: install.sgml,v 2.2 2006/07/18 14:48:50 david__schmidt Exp $ + $Id: install.sgml,v 2.3 2006/09/22 01:27:55 hal9 Exp $ Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org See LICENSE. diff --git a/doc/source/newfeatures.sgml b/doc/source/newfeatures.sgml index ef4c77c6..d1186690 100644 --- a/doc/source/newfeatures.sgml +++ b/doc/source/newfeatures.sgml @@ -3,7 +3,7 @@ Purpose : Entity included in other project documents. - $Id: newfeatures.sgml,v 2.3 2006/07/18 14:48:51 david__schmidt Exp $ + $Id: newfeatures.sgml,v 2.4 2006/09/22 01:27:55 hal9 Exp $ Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org See LICENSE. @@ -44,8 +44,9 @@ - Web page content filtering (removes banners based on size, - invisible web-bugs, JavaScript and HTML annoyances, pop-up windows, etc.) + Web page filtering (text replacements, removes banners based on size, + invisible web-bugs, JavaScript and HTML annoyances, + pop-up windows, header manipulation, etc.) diff --git a/doc/source/p-authors.sgml b/doc/source/p-authors.sgml index 027b8257..b13f77b9 100644 --- a/doc/source/p-authors.sgml +++ b/doc/source/p-authors.sgml @@ -3,7 +3,7 @@ Purpose : Entity included in other project documents. - $Id: p-authors.sgml,v 2.17 2006/10/22 14:23:34 hal9 Exp $ + $Id: p-authors.sgml,v 2.18 2006/10/22 14:29:34 hal9 Exp $ Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org See LICENSE. @@ -70,8 +70,9 @@ Current Privoxy Team: - Thanks to the many people who have tested Privoxy, reported bugs, made - suggestions or contributed in some way. These include (in alphabetical order): + Thanks to the many people who have tested Privoxy, reported bugs, provided + patches, made suggestions or contributed in some way. These include (in + alphabetical order): Ken Arromdee @@ -83,22 +84,29 @@ Current Privoxy Team: Michael T. Davis Mattes Dolak Peter E + Florian Effenberger + Dean Gaudet Aaron Hamid + Darel Henman Magnus Holmgren + Derek Jennings David Laight Don Libes Paul Lieverse Jindrich Makovicka David Mediavilla + Raphael Moll Oliver Stoeneberg + Martin Thomas Roberto Ragusa Félix Rauch Maynard Riley Spinor S Bart Schelstraete Bobby G. Vinyard - Darren Wiebe Jörg Weinmann + Darren Wiebe + Anduin Withers Oliver Yeoh Jamie Zawinski diff --git a/doc/source/privoxy-man-page.sgml b/doc/source/privoxy-man-page.sgml index 6df2d2b5..22c2ec8c 100644 --- a/doc/source/privoxy-man-page.sgml +++ b/doc/source/privoxy-man-page.sgml @@ -5,7 +5,7 @@ This file belongs into ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/ - $Id: privoxy-man-page.sgml,v 2.10 2006/10/03 11:12:18 hal9 Exp $ + $Id: privoxy-man-page.sgml,v 2.11 2006/10/24 10:57:00 hal9 Exp $ Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org See LICENSE. @@ -43,9 +43,9 @@ - - - + + + diff --git a/doc/source/readme.sgml b/doc/source/readme.sgml index 4e9d6513..08df5a94 100644 --- a/doc/source/readme.sgml +++ b/doc/source/readme.sgml @@ -4,10 +4,10 @@ - - - - + + + + @@ -17,7 +17,7 @@ Purpose : README for Privoxy - $Id: readme.sgml,v 2.7 2006/09/10 15:30:46 hal9 Exp $ + $Id: readme.sgml,v 2.8 2006/09/20 23:49:25 hal9 Exp $ Copyright (C) 2001 - 2006 Privoxy Developers http://privoxy.org See LICENSE. @@ -128,12 +128,18 @@ IMPORTANT CHANGES - BIG NEWS! September 2006, Privoxy 3.0.5 is released. This is a significant - upgrade with many new and enhanced features, and many bugs fixed. There are - fifteen new actions available, and several actions have enhanced - capabilities. Multiple filter files are now supported as well. See the - "What's New" section and the "Upgrader's Notes" in the User - Manual for details and specifics. + NEWS! November 2006, Privoxy 3.0.6 is released. This is a significant upgrade + with many new and enhanced features, and many bugs fixed. It is also the + first stable release in quite some time. There are fifteen new actions + available, and several actions have enhanced capabilities. Multiple filter + files are now supported as well. There are many improvements and refinements. + See the "What's New" section and the "Upgrader's Notes" in the + User Manual for details and specifics. Preliminary work on + 3.0.7 is already underway. + + + NEWS! September 2006, Privoxy 3.0.5 BETA is released. This is a significant + upgrade with many new and enhanced features, and many bugs fixed. There was and will not be an official 3.0.4 release. This release cycle @@ -252,7 +258,7 @@ - + diff --git a/doc/source/user-manual.sgml b/doc/source/user-manual.sgml index d687a862..dee74057 100644 --- a/doc/source/user-manual.sgml +++ b/doc/source/user-manual.sgml @@ -12,10 +12,10 @@ - + - - + + @@ -33,7 +33,7 @@ This file belongs into ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/ - $Id: user-manual.sgml,v 2.25 2006/10/18 10:50:33 hal9 Exp $ + $Id: user-manual.sgml,v 2.26 2006/10/24 11:16:44 hal9 Exp $ Copyright (C) 2001- 2006 Privoxy Developers http://www.privoxy.org See LICENSE. @@ -59,7 +59,7 @@ -$Id: user-manual.sgml,v 2.25 2006/10/18 10:50:33 hal9 Exp $ +$Id: user-manual.sgml,v 2.26 2006/10/24 11:16:44 hal9 Exp $ -Red Hat, SuSE and Conectiva RPMs +Red Hat and Fedora RPMs RPMs can be installed with rpm -Uvh privoxy-&p-version;-1.rpm, @@ -363,7 +363,8 @@ How to install the binary packages depends on your operating system: The most convenient way to obtain the Privoxy sources - is to download the source tarball from our project + is to download the source tarball from our + project download page. @@ -422,7 +423,7 @@ How to install the binary packages depends on your operating system: What's New in this Release - There are many improvements and new features since the last Privoxy stable release: + There are many improvements and new features since Privoxy 3.0.3, the last stable release: @@ -576,39 +577,11 @@ How to install the binary packages depends on your operating system: In addition, there are numerous bug fixes and significant enhancements, including error pages should no longer be cached if the problem is fixed, - much better DNS error handling, and various logging improvements. + much better DNS error handling, various logging improvements, and + configuration updates for better ad blocking and junk elimination. - - - The default actions setting is now Cautious. Previous - releases had a default setting of Medium. Experienced - users may want to adjust this, as it is fairly conservative by &my-app; - standards and past practices. See - http://config.privoxy.org/edit-actions-list?f=default. New users - should try the default settings for a while before turning up the volume. - - - The default setting has filtering turned off, which - subsequently means that compression is on. Remember - that filtering does not work on compressed pages, so if you use, or want to - use, filtering, you will need to force compression off. Example: - - - - { +filter{google} +prevent-compression } - .google. - - - Or if you use a number of filters, or filter many sites, you may just want - to turn off compression for all sites in - default.action (or - user.action). - - - @@ -673,11 +646,53 @@ How to install the binary packages depends on your operating system: default. This is primarily a matter of emphasis, but some features you may have been used to, may now be off by default. There are also a number of new actions and filters you may want to - consider, most of which are not incorporated into the default settings as - yet (see above). + consider, most of which are not fully incorporated into the default + settings as yet (see above). - + + + + The default actions setting is now Cautious. Previous + releases had a default setting of Medium. Experienced + users may want to adjust this, as it is fairly conservative by &my-app; + standards and past practices. See + http://config.privoxy.org/edit-actions-list?f=default. New users + should try the default settings for a while before turning up the volume. + + + + + + The default setting has filtering turned off, which + subsequently means that compression is on. Remember + that filtering does not work on compressed pages, so if you use, or want to + use, filtering, you will need to force compression off. Example: + + + + { +filter{google} +prevent-compression } + .google. + + + Or if you use a number of filters, or filter many sites, you may just want + to turn off compression for all sites in + default.action (or + user.action). + + + + + + + Also, session-cookies-only is + off by default now. If you've liked this feature in the past, you may want + to turn it back on in user.action now. + + + + @@ -687,6 +702,7 @@ How to install the binary packages depends on your operating system: + @@ -822,7 +838,8 @@ How to install the binary packages depends on your operating system: First a bit of a warning ... blocking ads is much like blocking SPAM: the more aggressive you are about it, the more likely you are to block - things that were not intended. So there is a trade off here. If you want + things that were not intended. And the more likely that some things + may not work as intended. So there is a trade off here. If you want extreme ad free browsing, be prepared to deal with more problem sites, and to spend more time adjusting the configuration to solve these unintended consequences. In short, there is @@ -835,7 +852,7 @@ How to install the binary packages depends on your operating system: Secondly, a brief explanation of Privoxy's actions. Actions in this context, are the directives we use to tell Privoxy to perform - some task relating to HTTP transactions (i.e. web browsing). We tell + some task relating to WWW transactions (i.e. web browsing). We tell Privoxy to take some action. Each action has a unique name and function. While there are many potential actions in Privoxy's @@ -860,13 +877,17 @@ How to install the binary packages depends on your operating system: original page's HTML content. An ad image for instance, is just an URL embedded in the page somewhere. The image itself may be on the same server, or a server somewhere else on the Internet. Complex web pages will have many - such embedded URLs. + such embedded URLs. &my-app; can deal with each URL individually, so, for + instance, the main page text is not touched, but images from such-and-such + server are blocked. - The actions we need to know about for ad blocking are: block, handle-as-image, and + linkend="handle-as-image">handle-as-image, + handle-as-empty-document,and set-image-blocker: @@ -875,12 +896,14 @@ How to install the binary packages depends on your operating system: - block - this action stops - any contact between your browser and any URL patterns that match this - action's configuration. It can be used for blocking ads, but also anything - that is determined to be unwanted. By itself, it simply stops any - communication with the remote server and sends Privoxy's - own built-in BLOCKED page instead to let you now what has happened. + block - this is perhaps + the single most used action, and is particularly important for ad blocking. + This action stops any contact between your browser and any URL patterns + that match this action's configuration. It can be used for blocking ads, + but also anything that is determined to be unwanted. By itself, it simply + stops any communication with the remote server and sends + Privoxy's own built-in BLOCKED page instead to + let you now what has happened (with some exceptions, see below). @@ -900,6 +923,15 @@ How to install the binary packages depends on your operating system: + + + handle-as-empty-document - + sends an empty document instead of Privoxy's + normal BLOCKED HTML page. This is useful for file types that are neither + HTML nor images, such as blocking JavaScript files. + + + Actions Files Tutorial. The ideas explained therein also apply to the web-based editor. + + There are also various + filters that can be used for ad blocking + (filters are a special subset of actions). These + fall into the advanced usage category, and are explained in + depth in later sections. + @@ -1082,7 +1121,7 @@ How to install the binary packages depends on your operating system: - With Firefox, this can be set under: + With Firefox, this is typically set under: @@ -1090,6 +1129,15 @@ How to install the binary packages depends on your operating system: + + Or optionally on some platforms: + + + + Edit -> Preferences -> General -> Connection Settings -> Manual Proxy Configuration + + + With Netscape (and @@ -1154,7 +1202,7 @@ How to install the binary packages depends on your operating system: -Red Hat, Fedora and Conectiva +Red Hat and Fedora A default Red Hat installation may not start &my-app; upon boot. It will use the file /etc/privoxy/config as its main configuration @@ -1190,6 +1238,9 @@ How to install the binary packages depends on your operating system: + Windows @@ -1631,7 +1682,7 @@ for details. default.action (which you will most probably want to define sooner or later) are probably best applied in user.action, where you can preserve them across - upgrades. standard.action is for + upgrades. standard.action is only for Privoxy's internal use. @@ -1773,7 +1824,7 @@ for details. - standard.action - is used by the web based editor + standard.action - is used only by the web based editor at http://config.privoxy.org/edit-actions-list?f=default, to set various pre-defined sets of rules for the default actions section @@ -2255,7 +2306,7 @@ for details. - While flexibile, this is not the sophistication of full regular expression based syntax. + While flexible, this is not the sophistication of full regular expression based syntax. @@ -2766,7 +2817,7 @@ new action # Check if www.example.net/ really uses valid XHTML -{+content-type-overwrite {application/xml}} +{ +content-type-overwrite{application/xml} } www.example.net/ # but leave the content type unmodified if the URL looks like a style sheet @@ -2856,7 +2907,7 @@ new action # Block the non-existent "Privacy-Violation:" client header -{+crunch-client-header {Privacy-Violation:}} +{ +crunch-client-header{Privacy-Violation:} } / @@ -2938,9 +2989,9 @@ new action # Let the browser revalidate cached documents without being tracked across sessions -{+hide-if-modified-since {-60} \ -+overwrite-last-modified {randomize} \ -+crunch-if-none-match} +{ +hide-if-modified-since{-60} \ + +overwrite-last-modified{randomize} \ + +crunch-if-none-match} / @@ -3092,7 +3143,7 @@ new action # Crunch server headers that try to prevent caching -{+crunch-server-header {no-cache}} +{ +crunch-server-header{no-cache} } / @@ -3963,7 +4014,7 @@ new action This action alone doesn't do anything noticeable. It just marks URLs. If the block action also applies, - the presence or absence of this mark decides whether an HTML blocked + the presence or absence of this mark decides whether an HTML BLOCKED page, or an empty document will be sent to the client as a substitute for the blocked content. The empty document isn't literally empty, but actually contains a single space. @@ -3994,6 +4045,8 @@ new action Some browsers complain about syntax errors if JavaScript documents are blocked with Privoxy's default HTML page; this option can be used to silence them. + And of course this action can also be used to eliminate the &my-app; + BLOCKED message in frames. The content type for the empty document can be specified with @@ -4270,10 +4323,10 @@ new action # Disarm the download link in Sourceforge's patch tracker -{-filter\ -+content-type-overwrite {text/plain}\ -+hide-content-disposition {block} } -.sourceforge.net/tracker/download.php +{ -filter \ + +content-type-overwrite{text/plain}\ + +hide-content-disposition{block} } + .sourceforge.net/tracker/download.php @@ -4358,9 +4411,9 @@ new action # Let the browser revalidate without being tracked across sessions -{+hide-if-modified-since {-60}\ -+overwrite-last-modified {randomize}\ -+crunch-if-none-match} +{ +hide-if-modified-since{-60} \ + +overwrite-last-modified{randomize} \ + +crunch-if-none-match} / @@ -5131,9 +5184,9 @@ new action # Let the browser revalidate without being tracked across sessions -{+hide-if-modified-since {-60}\ -+overwrite-last-modified {randomize}\ -+crunch-if-none-match} +{ +hide-if-modified-since{-60} \ + +overwrite-last-modified{randomize} \ + +crunch-if-none-match} / @@ -5767,7 +5820,7 @@ new action # These shops require pop-ups: # - {-kill-popups -filter{all-popups} -filter{unsolicted-popups}} + {-kill-popups -filter{all-popups} -filter{unsolicited-popups}} .dabs.com .overclockers.co.uk @@ -7828,8 +7881,9 @@ Requests Chain of Events - Let's take a quick look at the basic sequence of events when a web page is - requested by your browser and Privoxy is on duty: + Let's take a quick look at how some of Privoxy's + core features are triggered, and the ensuing sequence of events when a web + page is requested by your browser: @@ -7855,10 +7909,13 @@ Requests linkend="BLOCK">+block patterns. If so, the URL is then blocked, and the remote web server will not be contacted. +handle-as-image - is then checked and if it does not match, an - HTML BLOCKED page is sent back. Otherwise, if it does match, - an image is returned. The type of image depends on the setting of +set-image-blocker + and + +handle-as-empty-document + are then checked, and if there is no match, an + HTML BLOCKED page is sent back to the browser. Otherwise, if + it does match, an image is returned for the former, and an empty text + document for the latter. The type of image would depend on the setting of + +set-image-blocker (blank, checkerboard pattern, or an HTTP redirect to an image elsewhere). @@ -7886,8 +7943,8 @@ Requests - Now the web server starts sending its response back (i.e. typically a web page and related - data). + Now the web server starts sending its response back (i.e. typically a web + page). @@ -7910,7 +7967,7 @@ Requests - If a +filter + If any +filter action or +deanimate-gifs action applies (and the document type fits the action), the rest of the page is @@ -7923,7 +7980,7 @@ Requests Privoxy back to your browser. - If neither +filter + If neither a +filter action or +deanimate-gifs matches, then Privoxy passes the raw data through @@ -7935,14 +7992,22 @@ Requests As the browser receives the now (possibly filtered) page content, it reads and then requests any URLs that may be embedded within the page source, e.g. ad images, stylesheets, JavaScript, other HTML documents (e.g. - frames), sounds, etc. For each of these objects, the browser issues a new - request. And each such request is in turn processed as above. Note that a - complex web page may have many such embedded URLs. + frames), sounds, etc. For each of these objects, the browser issues a + separate request (this is easily viewable in Privoxy's + logs). And each such request is in turn processed just as above. Note that a + complex web page will have many, many such embedded URLs. If these + secondary requests are to a different server, then quite possibly a very + differing set of actions is triggered. + + NOTE: This is somewhat of a simplistic overview of what happens with each URL + request. For the sake of brevity and simplicity, we have focused on + Privoxy's core features only. + @@ -8437,7 +8502,7 @@ In file: user.action [ View ] [ Edit ]user.action, for local site exceptions. Note that when a simple domain pattern is used by itself (without the subsequent path portion), all sub-pages within that domain are included - automatcially in the scope of the action. + automatically in the scope of the action. @@ -8501,6 +8566,9 @@ In file: user.action [ View ] [ Edit ]