From: hal9 Date: Fri, 22 Sep 2006 01:27:55 +0000 (+0000) Subject: Final commit of probably various minor changes here and there. Unless X-Git-Tag: v_3_0_5~17 X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=commitdiff_plain;h=6cb41778d4fe473b3aa421acbee208a99f2df27b 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/announce.sgml b/doc/source/announce.sgml index 549d6b4e..b757e89e 100644 --- a/doc/source/announce.sgml +++ b/doc/source/announce.sgml @@ -5,10 +5,11 @@ - - - - + + + + + @@ -19,16 +20,14 @@ Purpose : Announcement text - $Id: announce.sgml,v 1.1.2.2 2002/08/30 02:52:11 hal9 Exp $ + $Id: announce.sgml,v 2.3 2006/07/18 14:48:50 david__schmidt Exp $ - Copyright (C) 2001, 2002 Privoxy Developers + Copyright (C) 2001-2006 Privoxy Developers http://www.privoxy.org See LICENSE. ======================================================================== NOTE: Please read developer-manual/documentation.html before touching - anything in this, or other Privoxy documentation. You have been warned! - Failure to abide by this rule will result in the revocation of your license - to live a peaceful existence! + anything in this, or other Privoxy documentation. ======================================================================== =================================================================== @@ -58,13 +57,7 @@ Announcing Privoxy - v.&p-version;. - - - + v.&p-version; @@ -72,6 +65,12 @@ &p-intro; + +New in this release + &newstuff; + + + &supported; @@ -108,6 +107,6 @@ -Privoxy Developers developers@privoxy.org +Privoxy Developers ijbswa-developers@lists.sourceforge.net diff --git a/doc/source/authors.sgml b/doc/source/authors.sgml index c2a1ba39..4f20931b 100644 --- a/doc/source/authors.sgml +++ b/doc/source/authors.sgml @@ -3,10 +3,10 @@ Purpose : AUTHORS file for Privoxy - $Id: authors.sgml,v 1.8 2002/05/10 01:48:19 hal9 Exp $ + $Id: authors.sgml,v 2.3 2006/07/18 14:48:50 david__schmidt Exp $ - Copyright (C) 2001, 2002 Privoxy Developers + Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org See LICENSE. ======================================================================== @@ -26,8 +26,8 @@ - - + + diff --git a/doc/source/buildsource.sgml b/doc/source/buildsource.sgml index b1f4db96..f87138e7 100644 --- a/doc/source/buildsource.sgml +++ b/doc/source/buildsource.sgml @@ -3,9 +3,9 @@ Purpose : Entity included in other project documents. - $Id: buildsource.sgml,v 2.6 2006/08/22 00:04:21 hal9 Exp $ + $Id: buildsource.sgml,v 2.7 2006/08/29 11:11:33 hal9 Exp $ - Copyright (C) 2001, 2002 Privoxy Developers + Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org See LICENSE. ====================================================================== diff --git a/doc/source/config.sgml b/doc/source/config.sgml index 1b6de2dc..a848b849 100644 --- a/doc/source/config.sgml +++ b/doc/source/config.sgml @@ -1,8 +1,8 @@ - - + + @@ -12,9 +12,9 @@ Purpose : config file generation - $Id: config.sgml,v 1.1.2.1 2002/05/29 02:01:02 hal9 Exp $ + $Id: config.sgml,v 2.3 2006/07/18 14:48:50 david__schmidt Exp $ - Copyright (C) 2001, 2002 Privoxy Developers + Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org See LICENSE. ======================================================================== diff --git a/doc/source/contacting.sgml b/doc/source/contacting.sgml index 59a89867..fd7c68ea 100644 --- a/doc/source/contacting.sgml +++ b/doc/source/contacting.sgml @@ -3,9 +3,9 @@ Purpose : Entity included in other project documents. - $Id: contacting.sgml,v 2.6 2006/08/27 22:01:55 hal9 Exp $ + $Id: contacting.sgml,v 2.7 2006/09/10 14:53:54 hal9 Exp $ - Copyright (C) 2001 - 2006 Privoxy Developers + Copyright (C) 2001 - 2006 Privoxy Developers http://privoxy.org See LICENSE. ====================================================================== @@ -201,7 +201,7 @@ Please be sure to provide the following information: The appendix - of the user manual also has helpful information + of the Privoxy User Manual also has helpful information on understanding actions, and action debugging. diff --git a/doc/source/copyright.sgml b/doc/source/copyright.sgml index 7d1335d0..ad08e08f 100644 --- a/doc/source/copyright.sgml +++ b/doc/source/copyright.sgml @@ -3,9 +3,9 @@ Purpose : Entity included in other project documents. - $Id: copyright.sgml,v 2.3 2006/07/18 14:48:50 david__schmidt Exp $ + $Id: copyright.sgml,v 2.4 2006/08/26 02:13:24 hal9 Exp $ - Copyright (C) 2001-2004 Privoxy Developers + Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org See LICENSE. ====================================================================== diff --git a/doc/source/developer-manual.sgml b/doc/source/developer-manual.sgml index 708dad10..78b5578e 100644 --- a/doc/source/developer-manual.sgml +++ b/doc/source/developer-manual.sgml @@ -8,8 +8,8 @@ - - + + @@ -23,9 +23,9 @@ This file belongs into ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/ - $Id: developer-manual.sgml,v 2.8 2006/08/22 23:35:01 hal9 Exp $ + $Id: developer-manual.sgml,v 2.9 2006/09/14 02:30:07 hal9 Exp $ - Copyright (C) 2001-2006 Privoxy Developers + Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org See LICENSE. ======================================================================== @@ -50,7 +50,7 @@ - $Id: developer-manual.sgml,v 2.8 2006/08/22 23:35:01 hal9 Exp $ + $Id: developer-manual.sgml,v 2.9 2006/09/14 02:30:07 hal9 Exp $ ource$ * * Purpose : (Fill me in with a good description!) * - * Copyright : Written by and Copyright (C) 2001 the SourceForge + * Copyright : Written by and Copyright (C) 2001-2006 the SourceForge * Privoxy team. http://www.privoxy.org/ * * Based on the Internet Junkbuster originally written @@ -1862,7 +1862,8 @@ const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 2.8 2006/08/22 23:35:0 * this file. If not, you can view it at * http://www.gnu.org/copyleft/gpl.html * or write to the Free Software Foundation, Inc., - * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA + * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 , + * USA * * Revisions : * $Log$ @@ -1892,14 +1893,14 @@ const char FILENAME_h_rcs[] = FILENAME_H_VERSION; #ifndef _FILENAME_H #define _FILENAME_H -#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 2.8 2006/08/22 23:35:01 hal9 Exp $" +#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 2.9 2006/09/14 02:30:07 hal9 Exp $" /********************************************************************* * * File : $Source$ * * Purpose : (Fill me in with a good description!) * - * Copyright : Written by and Copyright (C) 2001 the SourceForge + * Copyright : Written by and Copyright (C) 2001-2006 the SourceForge * Privoxy team. http://www.privoxy.org/ * * Based on the Internet Junkbuster originally written @@ -1921,8 +1922,9 @@ const char FILENAME_h_rcs[] = FILENAME_H_VERSION; * The GNU General Public License should be included with * this file. If not, you can view it at * http://www.gnu.org/copyleft/gpl.html - * or write to the Free Software Foundation, Inc., 59 - * Temple Place - Suite 330, Boston, MA 02111-1307, USA. + * or write to the Free Software Foundation, Inc., + * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 , + * USA * * Revisions : * $Log$ @@ -3023,6 +3025,10 @@ at sourceforge. Three simple steps: Temple Place - Suite 330, Boston, MA 02111-1307, USA. $Log: developer-manual.sgml,v $ + Revision 2.9 2006/09/14 02:30:07 hal9 + Fix ijbswa cvs links. Update notes on release process, and which config files + should be overwritten and which not. + Revision 2.8 2006/08/22 23:35:01 hal9 Fix email address, cvs URI, address branching changes and various other small updates. diff --git a/doc/source/faq.sgml b/doc/source/faq.sgml index f2877666..294349dc 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.16 2006/09/10 15:30:46 hal9 Exp $ + $Id: faq.sgml,v 2.17 2006/09/17 14:56:32 hal9 Exp $ Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org See LICENSE. @@ -77,7 +77,7 @@ -$Id: faq.sgml,v 2.16 2006/09/10 15:30:46 hal9 Exp $ +$Id: faq.sgml,v 2.17 2006/09/17 14:56:32 hal9 Exp $ - In the beginning, there was the + Along time ago, there was the Internet Junkbuster, by Anonymous Coders and Junkbusters - Corporation. It saved many users a lot of pain in the early days of + Corporation. This saved many users a lot of pain in the early days of web advertising and user tracking. But the web, its protocols and standards, and with it, the techniques for - forcing users to consume ads, give up autonomy over their browsing, and - for spying on them, kept evolving. Unfortunately, the Internet + forcing ads on users, give up autonomy over their browsing, and + for tracking them, keeps evolving. Unfortunately, the Internet Junkbuster did not. Version 2.0.2, published in 1998, was (and is) the last official release diff --git a/doc/source/install.sgml b/doc/source/install.sgml index afd630fc..a0b8affd 100644 --- a/doc/source/install.sgml +++ b/doc/source/install.sgml @@ -1,8 +1,8 @@ - - + + @@ -16,9 +16,9 @@ Purpose : INSTALL file for Privoxy - $Id: install.sgml,v 2.1.2.1 2002/10/24 22:07:39 hal9 Exp $ + $Id: install.sgml,v 2.2 2006/07/18 14:48:50 david__schmidt Exp $ - Copyright (C) 2001, 2002 Privoxy Developers + Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org See LICENSE. ======================================================================== @@ -58,7 +58,7 @@ * * Purpose : INSTALL file to help with installing from source. * - * Copyright : Written by and Copyright (C) 2001,2002 the SourceForge + * Copyright : Written by and Copyright (C) 2001-2006 the SourceForge * Privoxy team. http://www.privoxy.org/ * * Based on the Internet Junkbuster originally written @@ -80,8 +80,9 @@ * The GNU General Public License should be included with * this file. If not, you can view it at * http://www.gnu.org/copyleft/gpl.html - * or write to the Free Software Foundation, Inc., 59 - * Temple Place - Suite 330, Boston, MA 02111-1307, USA. + * or write to the Free Software Foundation, Inc., + * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, + * USA * *********************************************************************/ diff --git a/doc/source/license.sgml b/doc/source/license.sgml index a7f23798..9e49386d 100644 --- a/doc/source/license.sgml +++ b/doc/source/license.sgml @@ -3,9 +3,9 @@ Purpose : Entity included in other project documents. - $Id: license.sgml,v 2.3 2006/07/18 14:48:50 david__schmidt Exp $ + $Id: license.sgml,v 2.4 2006/09/10 14:02:05 hal9 Exp $ - Copyright (C) 2001-2006 Privoxy Developers + Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org See LICENSE. ====================================================================== diff --git a/doc/source/newfeatures.sgml b/doc/source/newfeatures.sgml index 9f1c209d..ef4c77c6 100644 --- a/doc/source/newfeatures.sgml +++ b/doc/source/newfeatures.sgml @@ -3,9 +3,9 @@ Purpose : Entity included in other project documents. - $Id: newfeatures.sgml,v 1.10 2002/05/15 03:54:29 hal9 Exp $ + $Id: newfeatures.sgml,v 2.3 2006/07/18 14:48:51 david__schmidt Exp $ - Copyright (C) 2001, 2002 Privoxy Developers + Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org See LICENSE. ====================================================================== diff --git a/doc/source/p-config.sgml b/doc/source/p-config.sgml index cdea8714..69efcb61 100644 --- a/doc/source/p-config.sgml +++ b/doc/source/p-config.sgml @@ -3,9 +3,9 @@ Purpose : Used with other docs and files only. - $Id: p-config.sgml,v 2.10 2006/09/07 02:02:56 hal9 Exp $ + $Id: p-config.sgml,v 2.11 2006/09/08 02:36:37 hal9 Exp $ - Copyright (C) 2001-2006 Privoxy Developers + Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org See LICENSE. ======================================================================== @@ -95,7 +95,7 @@ Sample Configuration File for Privoxy v&p-version; - $Id: p-config.sgml,v 2.10 2006/09/07 02:02:56 hal9 Exp $ + $Id: p-config.sgml,v 2.11 2006/09/08 02:36:37 hal9 Exp $ Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org @@ -523,6 +523,8 @@ II. FORMAT OF THE CONFIGURATION FILE No trailing /, please + @@ -862,7 +865,7 @@ actionsfile Specifies: - The trust file to use + The name of the trust file to use @@ -882,7 +885,7 @@ actionsfile Effect if unset: - The entire trust mechanism is turned off. + The entire trust mechanism is disabled. @@ -901,16 +904,19 @@ actionsfile Prepending a ~ character limits access to this site only (and any sub-paths within this site), e.g. - ~www.example.com. + ~www.example.com allows access to + ~www.example.com/features/news.html, etc. Or, you can designate sites as trusted referrers, by prepending the name with a + character. The effect is that access to untrusted sites will be granted -- but only if a link from this - trusted referrer was used. The link target will then be added to the - trustfile so that future, direct accesses will be granted. - Sites added via this mechanism do not become trusted referrers themselves - (i.e. they are added with a ~ designation). + trusted referrer was used to get there. The link target will then be added + to the trustfile so that future, direct accesses will be + granted. Sites added via this mechanism do not become trusted referrers + themselves (i.e. they are added with a ~ designation). + There is a limit of 512 such entries, after which new entries will not be + made. If you use the + operator in the trust file, it may grow @@ -1606,9 +1612,7 @@ ACLs: permit-access and deny-access multiple proxies. It can be used to better protect privacy and confidentiality when accessing specific domains by routing requests to those domains - through an anonymous public proxy (see e.g. http://www.multiproxy.org/anon_list.htm) - Or to use a caching proxy to speed up browsing. Or chaining to a parent + through an anonymous public proxy. Or to use a caching proxy to speed up browsing. Or chaining to a parent proxy may be necessary because the machine that Privoxy runs on has no direct Internet access. diff --git a/doc/source/privoxy-man-page.sgml b/doc/source/privoxy-man-page.sgml index 97c4c42a..b77e9565 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.7 2006/09/01 15:10:45 hal9 Exp $ + $Id: privoxy-man-page.sgml,v 2.8 2006/09/06 03:04:46 hal9 Exp $ - Copyright (C) 2001-2006 Privoxy Developers + Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org See LICENSE. ======================================================================== @@ -42,8 +42,8 @@ - - + + @@ -229,11 +229,14 @@ and Unix-like systems, these are located in /etc/privoxy/ by default. - - See the User Manual for a detailed - explanation of installation, general usage, all configuration options, new - features and notes on upgrading. + + 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 @@ -242,6 +245,12 @@ the same page. In addition, Privoxy can be toggled on/off. This is an internal page, and does not require Internet access. + + See the User Manual for a detailed + explanation of installation, general usage, all configuration options, new + features and notes on upgrading. + @@ -256,10 +265,10 @@ # Define a few useful custom aliases for later use {{alias}} - # Useful aliases + # Useful aliases that combine more than one action +crunch-cookies = +crunch-incoming-cookies +crunch-outgoing-cookies -crunch-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies - +imageblock = +block +handle-as-image + +block-as-image = +block +handle-as-image # Fragile sites should have the minimum changes fragile = -block -deanimate-gifs -fast-redirects -filter \ @@ -281,12 +290,12 @@ +deanimate-gifs{last} \ -downgrade-http-version \ -fast-redirects \ -+filter{js-annoyances} \ +-filter{js-annoyances} \ -filter{js-events} \ -+filter{html-annoyances} \ +-filter{html-annoyances} \ -filter{content-cookies} \ +filter{refresh-tags} \ -+filter{unsolicited-popups} \ +-filter{unsolicited-popups} \ -filter{all-popups} \ +filter{img-reorder} \ +filter{banners-by-size} \ @@ -331,22 +340,23 @@ # Block, and treat these URL patterns as if they were 'images'. # We would expect these to be ads. - {+imageblock} + { +block-as-image } .ad.doubleclick.net .a[0-9].yimg.com/(?:(?!/i/).)*$ ad.*.doubleclick.net - # Block any URLs that match these patterns - {+block} + # Block all URLs that match these patterns + { +block } ad*. .*ads. banner?. /.*count(er)?\.(pl|cgi|exe|dll|asp|php[34]?) .hitbox.com + media./.*(ads|banner) # Make exceptions for these harmless ones that would be # caught by our +block patterns just above. - {-block} + { -block } adsl. advice. .*downloads. @@ -367,15 +377,20 @@ # Set personal exceptions to the policies in default.action ####### - # Sites where we want persistant cookies, so allow *all* cookies - {-crunch-cookies -session-cookies-only} + # Sites where we want persistent cookies, so allow *all* cookies + { -crunch-cookies -session-cookies-only } .redhat.com .sun.com .msdn.microsoft.com - # This site breaks easily. - {-block -fast-redirects} + # These sites breaks easily. Use our "fragile" alias here. + { fragile } .forbes.com + mybank.example.com + + # Replace example.com's style sheet with one of my choosing + { +redirect{http://localhost/css-replacements/example.com.css} } + example.com/stylesheet.css diff --git a/doc/source/seealso.sgml b/doc/source/seealso.sgml index 567becc6..326944c0 100644 --- a/doc/source/seealso.sgml +++ b/doc/source/seealso.sgml @@ -3,9 +3,9 @@ Purpose : Entity included in other project documents. - $Id: seealso.sgml,v 2.4 2006/08/26 10:46:27 hal9 Exp $ + $Id: seealso.sgml,v 2.5 2006/09/04 12:39:55 hal9 Exp $ - Copyright (C) 2001-2006 Privoxy Developers + Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org See LICENSE. ====================================================================== @@ -101,7 +101,7 @@ dead link 08/26/06 --> - http://privacy.net/analyze/, a useful site + http://privacy.net/, a useful site to check what information about you is leaked while you browse the web. @@ -114,7 +114,7 @@ dead link 08/26/06 http://tor.eff.org/, - TOR can help anonymize web browsing, + Tor can help anonymize web browsing, web publishing, instant messaging, IRC, SSH, and other applications. diff --git a/doc/source/supported.sgml b/doc/source/supported.sgml index 0ce0cc35..2ee218ec 100644 --- a/doc/source/supported.sgml +++ b/doc/source/supported.sgml @@ -3,9 +3,9 @@ Purpose : Entity included in other project documents. - $Id: supported.sgml,v 2.5 2006/07/18 14:48:51 david__schmidt Exp $ + $Id: supported.sgml,v 2.6 2006/09/02 14:15:52 hal9 Exp $ - Copyright (C) 2001-2006 Privoxy Developers + Copyright (C) 2001-2006 Privoxy Developers http://privoxy.org See LICENSE. ====================================================================== diff --git a/doc/source/user-manual.sgml b/doc/source/user-manual.sgml index 217f5a6f..0cadea86 100644 --- a/doc/source/user-manual.sgml +++ b/doc/source/user-manual.sgml @@ -11,8 +11,8 @@ - - + + @@ -33,9 +33,9 @@ This file belongs into ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/ - $Id: user-manual.sgml,v 2.20 2006/09/10 14:53:54 hal9 Exp $ + $Id: user-manual.sgml,v 2.21 2006/09/20 03:21:36 david__schmidt Exp $ - Copyright (C) 2001- 2006 Privoxy Developers + Copyright (C) 2001- 2006 Privoxy Developers http://www.privoxy.org See LICENSE. ======================================================================== @@ -59,7 +59,7 @@ -$Id: user-manual.sgml,v 2.20 2006/09/10 14:53:54 hal9 Exp $ +$Id: user-manual.sgml,v 2.21 2006/09/20 03:21:36 david__schmidt Exp $ - You can find the latest version of the User Manual at Privoxy User Manual at http://www.privoxy.org/user-manual/. Please see the Contact section on how to contact the developers. @@ -136,7 +136,8 @@ Hal. Features In addition to the core - features of ad blocking and cookie management, + features of ad blocking and + cookie management, Privoxy provides many supplemental features, that give the end-user more control, more privacy and more freedom: @@ -224,7 +225,7 @@ How to install the binary packages depends on your operating system: in the same directory as you installed Privoxy in. - Version 3.0.4 introduces full Windows service + Version 3.0.4 introduced full Windows service functionality. On Windows only, the Privoxy program has two new command line arguments to install and uninstall Privoxy as a service. @@ -431,7 +432,7 @@ How to install the binary packages depends on your operating system: Multiple filter files can now be specified in config. This allows for locally defined filters that can be maintained separately from the filters as - supplied by the developers. + supplied by the developers, i.e. default.filter. @@ -558,7 +559,8 @@ How to install the binary packages depends on your operating system: - Actions files problems and suggestions are now being directed to: http://sourceforge.net/tracker/?group_id=11118&atid=460288. + Actions files problems and suggestions are now being directed to: + http://sourceforge.net/tracker/?group_id=11118&atid=460288. Please use this to report such configuration related problems as missed ads, sites that don't function properly due to one action or another, innocent images being blocked, etc. @@ -567,12 +569,23 @@ How to install the binary packages depends on your operating system: - In addition, there are various 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. + 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. + + + 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. + + @@ -598,7 +611,7 @@ How to install the binary packages depends on your operating system: - On the other hand, some installers may not overwrite any existing configuration + On the other hand, other installers may not overwrite any existing configuration files, thinking you will want to do that. You may want to manually check your saved files against the newer versions to see if the improvements have merit, or whether there are new options that you may want to consider. @@ -610,12 +623,23 @@ How to install the binary packages depends on your operating system: See the full documentation on fast-redirects - which has changed syntax, and may require adjustments to local configs. + which has changed syntax, and will require adjustments to local configs, + such as user.action. You must reference the new + syntax: + + + { +fast-redirects{check-decoded-url} } + .example.com + mybank.com + .google. + + - The jarfile, cookie logger, is off by default now. + The jarfile, + cookie logger, is off by default now. @@ -625,6 +649,8 @@ How to install the binary packages depends on your operating system: and you may want to review which actions are on by 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 you may want to consider, most of + which are not incorporated into the default settings as yet (see above). @@ -676,7 +702,8 @@ How to install the binary packages depends on your operating system: Set your browser to use Privoxy as HTTP and - HTTPS (SSL) proxy by setting the proxy configuration for address of + HTTPS (SSL) proxy + by setting the proxy configuration for address of 127.0.0.1 and port 8118. DO NOT activate proxying for FTP or any protocols besides HTTP and HTTPS (SSL)! It won't work! @@ -686,8 +713,9 @@ How to install the binary packages depends on your operating system: Flush your browser's disk and memory caches, to remove any cached ad images. - If using Privoxy to manage cookies, you should - remove any currently stored cookies too. + If using Privoxy to manage + cookies, + you should remove any currently stored cookies too. @@ -701,24 +729,24 @@ How to install the binary packages depends on your operating system: See the Configuration section for more configuration options, and how to customize your installation. - next section for a quick introduction to how Privoxy blocks ads and - banners.]]> + banners. - If you experience ads that slipped through, innocent images that are + If you experience ads that slip through, innocent images that are blocked, or otherwise feel the need to fine-tune - Privoxy's behaviour, take a look at the Privoxy's behavior, take a look at the actions files. As a quick start, you might find the richly commented examples helpful. You can also view and edit the actions files through the web-based user interface. The - Appendix Anatomy of an - Action has hints how to debug actions that + Appendix Troubleshooting: Anatomy of an + Action has hints how to understand and debug actions that misbehave. @@ -1002,7 +1030,8 @@ How to install the binary packages depends on your operating system: Before launching Privoxy for the first time, you will want to configure your browser(s) to use - Privoxy as a HTTP and HTTPS (SSL) proxy. The default is + Privoxy as a HTTP and HTTPS (SSL) + proxy. The default is 127.0.0.1 (or localhost) for the proxy address, and port 8118 (earlier versions used port 8000). This is the one configuration step that must be done ! @@ -1062,7 +1091,7 @@ How to install the binary packages depends on your operating system: Then, check Use Proxy and fill in the appropriate info (Address: 127.0.0.1, Port: 8118). Include HTTPS (SSL), if you want HTTPS - proxy support too (sometimes labeled Secure. Make sure any + proxy support too (sometimes labeled Secure). Make sure any checkboxes like Use the same proxy server for all protocols is UNCHECKED. You want only HTTP and HTTPS (SSL)! @@ -1086,8 +1115,9 @@ How to install the binary packages depends on your operating system: After doing this, flush your browser's disk and memory caches to force a re-reading of all pages and to get rid of any ads that may be cached. Remove - any cookies, if you want Privoxy to manage that. You - are now ready to start enjoying the benefits of using + any cookies, + if you want Privoxy to manage that. You are now + ready to start enjoying the benefits of using Privoxy! @@ -1436,8 +1466,8 @@ must find a better place for this paragraph - On MS Windows only there are two addition - options to allow Privoxy to install and + On MS Windows only there are two additional + command-line options to allow Privoxy to install and run as a service. See the Window Installation section for details. @@ -1612,7 +1642,10 @@ for details. The syntax of all configuration files has remained the same throughout the 3.x series. There have been enhancements, but no changes that would preclude - the use of any configuration file from one version to the next. + the use of any configuration file from one version to the next. (There is + one exception: +fast-redirects which + has enhanced syntax and will require updating any local configs from earlier + versions.) @@ -1622,7 +1655,7 @@ for details. in a line. If the # is preceded by a backslash, it looses its special function. Placing a # in front of an otherwise valid configuration line to prevent it from being interpreted is called "commenting - out" that line. + out" that line. Blank lines are ignored. @@ -1680,7 +1713,8 @@ for details. There are a number of such actions, with a wide range of functionality. Each action does something a little different. These actions give us a veritable arsenal of tools with which to exert - our control, preferences and independence. + our control, preferences and independence. Actions can be combined so that + their effects are aggregated when applied against a given set of URLs. There @@ -1696,13 +1730,13 @@ for details. that sets the initial values for all actions. It is intended to provide a base level of functionality for Privoxy's array of features. So it is - a set of broad rules that should work reasonably well for users everywhere. + a set of broad rules that should work reasonably well as-is for most users. This is the file that the developers are keeping updated, and making available to users. - It is also the file that keeps track of the user's preferences - as set in standard.action, e.g. either - cautious, medium, or - adventuresome. + The user's preferences as set in standard.action, + e.g. either Cautious (the default), + Medium, or Advanced (see + below). @@ -1722,12 +1756,15 @@ for details. in default.action. - Edit Set to Cautious Set to Medium Set to Adventuresome + Edit Set to Cautious Set to Medium Set to Advanced These have increasing levels of aggressiveness and have no influence on your browsing unless you select them explicitly in the - editor. + editor. A default installation should be pre-set to + Cautious (versions prior to 3.0.5 were set to + Medium). New users should try this for a while before + adjusting the settings to more aggressive levels. The Edit button allows you to turn each @@ -1736,7 +1773,7 @@ for details. a minimal set of &my-app;'s features, and subsequently there will be less of a chance for accidental problems. The Medium button sets the list to a medium level of ad blocking and a low level set of - privacy features. The Adventuresome button + privacy features. The Advanced button sets the list to a high level of ad blocking and medium level of privacy. See the chart below. The latter three buttons over-ride any changes via with the Edit button. More @@ -1762,7 +1799,7 @@ for details. Feature Cautious Medium - Adventuresome + Advanced @@ -1777,9 +1814,9 @@ for details. Ad-blocking Aggressiveness - low medium high + high @@ -1797,16 +1834,16 @@ for details. Pop-up killing - no - unsolicited + blocks only + blocks only all Privacy Features - none low medium + medium/high @@ -1883,7 +1920,14 @@ for details. user.action). The content of these can all be viewed and edited from http://config.privoxy.org/show-status. - + The over-riding principle when applying actions, is that the last action that + matches a given URL, wins. The broadest, most general rules go first + (defined in default.action), + followed by any exceptions (typically also in + default.action), which are then followed lastly by any + local preferences (typically in user.action). + Generally, user.action has the last word. + An actions file typically has multiple sections. If you want to use @@ -1916,7 +1960,8 @@ for details. Note that some actions, like cookie suppression or script disabling, may render some sites unusable that rely on these techniques to work properly. Finding the right mix of actions is not always easy and - certainly a matter of personal taste. In general, it can be said that the more + certainly a matter of personal taste. And, things can always change, requiring + refinements in the configuration. 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 make later. If, for example, you want to crunch all cookies per @@ -1942,16 +1987,16 @@ for details. url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status. The editor allows both fine-grained control over every single feature on a per-URL basis, and easy choosing from wholesale sets of defaults like - Cautious, Medium or Adventuresome. - Warning: the Adventuresome setting is not only more aggressive, - but includes settings that are fun and subversive, and which some may find of - dubious merit! + Cautious, Medium or Advanced. + Warning: the Advanced setting is more aggressive, and + will be more likely to cause problems for some sites. Experienced users only! If you prefer plain text editing to GUIs, you can of course also directly edit the - the actions files. Look at default.action which is richly - commented. + the actions files with your favorite text editor. Look at + default.action which is richly commented with many + good examples. @@ -1978,17 +2023,28 @@ for details. +handle-as-image }, then later another one with just { +block }, resulting - in both actions to apply. + in both actions to apply. And there may well be + cases where you will want to combine actions together. Such a section then + might look like: + + + { +handle-as-image +block } + # Block these as if they were images. Send no block page. + banners.example.com + media.example.com/.*banners + .example.com/images/ads/ + + You can trace this process for any given URL by visiting http://config.privoxy.org/show-url-info. - More detail on this is provided in the Appendix, - Anatomy of an Action. + Examples and more detail on this is provided in the Appendix, + Troubleshooting: Anatomy of an Action section. @@ -1997,9 +2053,9 @@ for details. Patterns As mentioned, Privoxy uses patterns - to determine what actions might apply to which sites and pages your browser - attempts to access. These patterns use wild card type - pattern matching to achieve a high degree of + to determine what actions might apply to which sites and + pages your browser attempts to access. These patterns use wild + card type pattern matching to achieve a high degree of flexibility. This allows one expression to be expanded and potentially match against many similar patterns. @@ -2013,6 +2069,13 @@ for details. http://) should not be included in the pattern. This is assumed already! + + The pattern matching syntax is different for the domain and path parts of + the URL. The domain part uses a simple globbing type matching technique, + while the path part uses a more flexible + Regular + Expressions (PCRE) based syntax. + @@ -2020,7 +2083,9 @@ for details. is a domain-only pattern and will match any request to www.example.com, - regardless of which document on that server is requested. + regardless of which document on that server is requested. So ALL pages in + this domain would be covered by the scope of this action. Note that a + simple example.com is different and would NOT match. @@ -2047,7 +2112,7 @@ for details. matches the document /index.html, regardless of the domain, - i.e. on any web server. + i.e. on any web server anywhere. @@ -2056,7 +2121,8 @@ for details. matches nothing, since it would be interpreted as a domain name and - there is no top-level domain called .html. + there is no top-level domain called .html. So its + a mistake. @@ -2095,8 +2161,14 @@ for details. .example. - matches any domain that CONTAINS .example. - (Correctly speaking: It matches any FQDN that contains example as a domain.) + matches any domain that CONTAINS .example.. + And, by the way, also included would be any files or documents that exist + within that domain since no path limitations are specified. (Correctly + speaking: It matches any FQDN that contains example as + a domain.) This might be www.example.com, + news.example.de, or + www.example.net/cgi/testing.pl for instance. All these + cases are matched. @@ -2104,10 +2176,15 @@ for details. Additionally, there are wild-cards that you can use in the domain names - themselves. They work pretty similar to shell wild-cards: * - stands for zero or more arbitrary characters, ? stands for - any single character, you can define character classes in square - brackets and all of that can be freely mixed: + themselves. These work similarly to shell globbing type wild-cards: + * represents zero or more arbitrary characters (this is + equivalent to the + Regular + Expression based syntax of .*), + ? represents any single character (this is equivalent to the + regular expression syntax of a simple .), and you can define + character classes in square brackets which is similar to + the same regular expression technique. All of this can be freely mixed: @@ -2150,6 +2227,10 @@ for details. + + While flexibile, this is not the sophistication of full regular expression based syntax. + + @@ -2159,9 +2240,11 @@ for details. The Path Pattern - Privoxy uses Perl compatible regular expressions + Privoxy uses Perl compatible (PCRE) + Regular + Expression based syntax (through the PCRE library) for - matching the path. + matching the path portion (after the slash), and is thus more flexible. @@ -2186,6 +2269,72 @@ for details. only documents whose path starts with PaTtErN in exactly this capitalization. + + + + .example.com/.* + + + Is equivalent to just .example.com, since any documents + within that domain are matched with or without the .* + regular expression. This is redundant + + + + + .example.com/.*/index.html + + + Will match any page in the domain of example.com that is + named index.html, and that is part of some path. For + example, it matches www.example.com/testing/index.html but + NOT www.example.com/index.html because the regular + expression called for at least two /'s, thus the path + requirement. It also would match + www.example.com/testing/index_html, because of the + special meta-character .. + + + + + .example.com/(.*/)?index\.html + + + This regular expression is conditional so it will match any page + named index.html regardless of path which in this case can + have one or more /'s. And this one must contain exactly + .html (but does not have to end with that!). + + + + + .example.com/(.*/)(ads|banners?|junk) + + + This regular expression will match any path of example.com + that contains any of the words ads, banner, + banners (because of the ?) or junk. + The path does not have to end in these words, just contain them. + + + + + .example.com/(.*/)(ads|banners?|junk)/.*\.(jpe?g|gif|png)$ + + + This is very much the same as above, except now it must end in either + .jpg, .jpeg, .gif or .png. So this + one is limited to common image formats. + + + + + + + There are many, many good examples to be found in default.action, + and more tutorials below in Appendix on regular expressions. + + @@ -2219,7 +2368,7 @@ for details. - There are three classes of actions: + Actions fall into three categories: @@ -2296,12 +2445,13 @@ for details. Later defined actions always over-ride earlier ones. So exceptions to any rules you make, should come in the latter part of the file (or - in a file that is processed later when using multiple actions files). For - multi-valued actions, the actions are applied in the order they are specified. - Actions files are processed in the order they are defined in - config (the default installation has three actions - files). It also quite possible for any given URL pattern to match more than - one pattern and thus more than one set of actions! + in a file that is processed later when using multiple actions files such + as user.action). For multi-valued actions, the actions + are applied in the order they are specified. Actions files are processed in + the order they are defined in config (the default + installation has three actions files). It also quite possible for any given + URL pattern to match more than one pattern and thus more than one set of + actions! Last match wins. @@ -2398,10 +2548,16 @@ for details. Effect: - Requests for URLs to which this action applies are blocked, i.e. the requests are not - forwarded to the remote server, but answered locally with a substitute page or image, - as determined by the handle-as-image - and set-image-blocker actions. + Requests for URLs to which this action applies are blocked, i.e. the + requests are trapped by &my-app; and the requested URL is never retrieved, + but is answered locally with a substitute page or image, as determined by + the handle-as-image, + set-image-blocker, and + handle-as-empty-document actions. + @@ -2446,7 +2602,8 @@ for details. It is important to understand this process, in order to understand how Privoxy deals with - ads and other unwanted content. + ads and other unwanted content. Blocking is a core feature, and one + upon which various other features depend. The filter @@ -2462,12 +2619,18 @@ for details. Example usage (section): - {+block} # Block and replace with "blocked" page -.nasty-stuff.example.com - -{+block +handle-as-image} # Block and replace with image -.ad.doubleclick.net -.ads.r.us + {+block} +# Block and replace with "blocked" page + .nasty-stuff.example.com + +{+block +handle-as-image} +# Block and replace with image + .ad.doubleclick.net + .ads.r.us/banners/ + +{+block +handle-as-empty-document} +# Block and then ignore + adserver.exampleclick.net/.*\.js$ @@ -2577,6 +2740,7 @@ new action # Check if www.example.net/ really uses valid XHTML {+content-type-overwrite {application/xml}} www.example.net/ + # but leave the content type unmodified if the URL looks like a style sheet {-content-type-overwrite} www.example.net/*.\.css$ @@ -3221,10 +3385,12 @@ problem-host.example.com Example usage: - +fast-redirects{simple-check} - - - +fast-redirects{check-decoded-url} + + { +fast-redirects{simple-check} } + .example.com + + { +fast-redirects{check-decoded-url} } + another.example.com/testing @@ -3254,8 +3420,9 @@ problem-host.example.com based substitutions. (Note: as of version 3.0.3 plain text documents are exempted from filtering, because web servers often use the text/plain MIME type for all files whose type they - don't know.) By default, filtering works only on the document content - itself, not the headers. + don't know.) By default, filtering works only on the raw document content + itself (that which can be seen with View Source), + not the headers. @@ -3282,7 +3449,7 @@ problem-host.example.com When used in its negative form, - and without parameters, filtering is completely disabled. + and without parameters, all filtering is completely disabled. @@ -3303,8 +3470,13 @@ problem-host.example.com noticeable on slower connections. - This is very powerful feature, and rolling your own - filters requires a knowledge of regular expressions and HTML. + Rolling your own + filters requires a knowledge of + Regular + Expressions and + HTML. + This is very powerful feature, and potentially very intrusive. Use + with caution. The amount of data that can be filtered is limited to the @@ -3314,15 +3486,15 @@ problem-host.example.com data, and all pending data, is passed through unfiltered. - Inadequate MIME types, such as zipped files, are not filtered at all. + Inappropriate MIME types, such as zipped files, are not filtered at all. (Again, only text-based types except plain text). Encrypted SSL data (from HTTPS servers) cannot be filtered either, since this would violate the integrity of the secure transaction. In some situations it might be necessary to protect certain text, like source code, from filtering - by defining appropriate -filter sections. + by defining appropriate -filter exceptions. - At this time, Privoxy cannot (yet!) uncompress compressed + At this time, Privoxy cannot uncompress compressed documents. If you want filtering to work on all documents, even those that would normally be sent compressed, use the prevent-compression @@ -4937,9 +5109,9 @@ new action Notes: - This action is useful to replace whole documents with your own - ones. For that to work, they have to be available on another server, - and both should resolve. + This action is useful to replace whole documents with ones of your + choosing. This can be used to enforce safe surfing, or just as a simple + convenience. You can do the same by combining the actions @@ -4957,12 +5129,16 @@ new action - Example usage: + Example usages: # Replace example.com's style sheet with another one -{+redirect{http://localhost/css-replacements/example.com.css}} -example.com/stylesheet.css +{ +redirect{http://localhost/css-replacements/example.com.css} } + example.com/stylesheet.css + +# Create a short, easy to remember nickname for a favorite site +{ +redirect{http://www.privoxy.org/user-manual/actions-file.html} } + a @@ -5469,7 +5645,7 @@ new action # +crunch-all-cookies = +crunch-incoming-cookies +crunch-outgoing-cookies -crunch-all-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies - block-as-image = +block +handle-as-image + +block-as-image = +block +handle-as-image mercy-for-cookies = -crunch-all-cookies -session-cookies-only -filter{content-cookies} # These aliases define combinations of actions @@ -5581,7 +5757,7 @@ that also explains why and how aliases are used: # +crunch-all-cookies = +crunch-incoming-cookies +crunch-outgoing-cookies -crunch-all-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies - block-as-image = +block +handle-as-image + +block-as-image = +block +handle-as-image mercy-for-cookies = -crunch-all-cookies -session-cookies-only -filter{content-cookies} # These aliases define combinations of actions @@ -5805,7 +5981,7 @@ edit.*.yahoo.com generate the banners, so it won't be visible from the URL that the request is for an image. Hence we block them and mark them as images in one go, with the help of our - block-as-image alias defined above. (We could of + +block-as-image alias defined above. (We could of course just as well use +block +handle-as-image here.) Remember that the type of the replacement image is chosen by the @@ -5819,7 +5995,7 @@ edit.*.yahoo.com # Known ad generators: # -{ block-as-image } +{ +block-as-image } ar.atwola.com .ad.doubleclick.net .ad.*.doubleclick.net @@ -6027,12 +6203,10 @@ handle-as-text = -filter +-filter } -.your-home-banking-site.com + .your-home-banking-site.com @@ -6077,8 +6251,8 @@ stupid-server.example.com/ { +block } -www.example.com/nasty-ads/sponsor.gif -another.popular.site.net/more/junk/here/ + www.example.com/nasty-ads/sponsor.gif + another.popular.site.net/more/junk/here/ @@ -6096,9 +6270,10 @@ another.popular.site.net/more/junk/here/ { +block-as-image } -.doubleclick.net -/Realmedia/ads/ -ar.atwola.com/ + .doubleclick.net + .fastclick.net + /Realmedia/ads/ + ar.atwola.com/ @@ -6109,13 +6284,16 @@ ar.atwola.com/ -- whoa! -- it worked. The fragile aliases disables those actions that are most likely to break a site. Also, good for testing purposes to see if it is Privoxy - that is causing the problem or not. + that is causing the problem or not. We later find other regular sites + that misbehave, and add those to our personalized list of troublemakers: { fragile } -.forbes.com + .forbes.com + mail.example.com + .mybank.com @@ -6128,7 +6306,7 @@ ar.atwola.com/ { +filter{fun} } -/ # For ALL sites! + / # For ALL sites! @@ -6149,9 +6327,9 @@ ar.atwola.com/ { allow-ads } -.sourceforge.net -.slashdot.org -.osdn.net + .sourceforge.net + .slashdot.org + .osdn.net @@ -6171,7 +6349,7 @@ ar.atwola.com/ { handle-as-text } -/.*\.sh$ + /.*\.sh$ @@ -6234,7 +6412,7 @@ ar.atwola.com/ Substitutions are made at the source level, so if you want to roll your own filters, you should first be familiar with HTML syntax, and, of course, regular expressions. By default, filters are only applied - to the document content, but can be extended to the headers with + to the raw document content, but can be extended to the HTTP headers with the supplemental actions: filter-client-headers and filter-server-headers. @@ -6282,7 +6460,9 @@ ar.atwola.com/ - If you are new to regular expressions, you might want to take a look at + If you are new to + Regular + Expressions, you might want to take a look at the Appendix on regular expressions, and see the Perl manual for @@ -6879,7 +7059,7 @@ pre-defined filters for your convenience: -Templates +Privoxy's Template Files All Privoxy built-in pages, i.e. error pages such as the 404 - No Such Domain @@ -7577,7 +7757,7 @@ Requests -Anatomy of an Action +Troubleshooting: Anatomy of an Action The way Privoxy applies @@ -7599,6 +7779,13 @@ Requests and easy way to do this (be sure to flush caches afterward!). Looking at the logs is a good idea too. + + Another easy troubleshooting step to try is if you have done any + customization of your installation, revert back to the installed + defaults and see if that helps. There are times the developers get complaints + about one thing or another, and the problem is more related to a customized + configuration issue. + Privoxy also provides the @@ -7716,41 +7903,42 @@ In file: user.action [ View ] [ Edit ] The first listing - is any matches for the standard.action file. No hits at - all here on standard. Then next is default, or - our default.action file. The large, multi-line listing, - is how the actions are set to match for all URLs, i.e. our default settings. - If you look at your actions file, this would be the section - just below the aliases section near the top. This will apply to - all URLs as signified by the single forward slash at the end of the listing - -- /. - - - - But we can define additional actions that would be exceptions to these general - rules, and then list specific URLs (or patterns) that these exceptions would - apply to. Last match wins. Just below this then are two explicit matches for - .google.com. The first is negating our previous cookie setting, - which was for default.action file. The large, multi-line + listing, is how the actions are set to match for all URLs, i.e. our default + settings. If you look at your actions file, this would be the + section just below the aliases section near the top. This + will apply to all URLs as signified by the single forward slash at the end + of the listing -- / . + + + + But we have defined additional actions that would be exceptions to these general + rules, and then we list specific URLs (or patterns) that these exceptions + would apply to. Last match wins. Just below this then are two explicit + matches for .google.com. The first is negating our previous + cookie setting, which was for +session-cookies-only (i.e. not persistent). So we will allow persistent cookies for google, at least that is how it is in this example. The second turns - off any - off any +fast-redirects action, allowing this to take place unmolested. Note that there is a leading dot here -- .google.com. This will match any hosts and sub-domains, in the google.com domain also, such as - www.google.com. So, apparently, we have these two actions - defined somewhere in the lower part of our default.action - file, and google.com is referenced somewhere in these latter - sections. + www.google.com or mail.google.com. But it would not + match www.google.de! So, apparently, we have these two actions + defined as exceptions to the general rules at the top somewhere in the lower + part of our default.action file, and + google.com is referenced somewhere in these latter sections. Then, for our user.action file, we again have no hits. So there is nothing google-specific that we might have added to our own, local - configuration. + configuration. If there was, those actions would over-rule any actions from + previously processed files, such as default.action. + user.action typically has the last word. This is the + best place to put hard and fast exceptions, @@ -7824,22 +8012,23 @@ In file: user.action [ View ] [ Edit ] - { +block +handle-as-image } - .ad.doubleclick.net - - { +block +handle-as-image } + { +block } ad*. + { +block } + .ad. + { +block +handle-as-image } - .doubleclick.net + .[a-vx-z]*.doubleclick.net - We'll just show the interesting part here, the explicit matches. It is - matched three different times. Each as an +block +handle-as-image, + We'll just show the interesting part here - the explicit matches. It is + matched three different times. Two +block sections, + and a +block +handle-as-image, which is the expanded form of one of our aliases that had been defined as: - +imageblock. (+block-as-image. (Aliases are defined in the first section of the actions file and typically used to combine more than one action.) @@ -7854,10 +8043,9 @@ In file: user.action [ View ] [ Edit ]+block and an - +handle-as-image. - The custom alias +imageblock just simplifies the process and make - it more readable. + +handle-as-image. + The custom alias +block-as-image just + simplifies the process and make it more readable. @@ -7922,10 +8110,15 @@ In file: user.action [ View ] [ Edit ] Ooops, the /adsl/ is matching /ads in our configuration! But we did not want this at all! Now we see why we get the - blank page. We could now add a new action below this that explicitly - un blocks ({-block}) paths with - adsl in them (remember, last match in the configuration wins). - There are various ways to handle such exceptions. Example: + blank page. It is actually triggering two different actions here, and + the effects are aggregated so that the URL is blocked, and &my-app; is told + to treat the block as if it were an image. But this is, of course, all wrong. + We could now add a new action below this (or better in our own + user.action file) that explicitly + un blocks ( + {-block}) paths with + adsl in them (remember, last match in the configuration + wins). There are various ways to handle such exceptions. Example: @@ -7937,8 +8130,10 @@ In file: user.action [ View ] [ Edit ] - Now the page displays ;-) Be sure to flush your browser's caches when - making such changes. Or, try using Shift+Reload. + Now the page displays ;-) + Remember to flush your browser's caches when making these kinds of changes to + your configuration to insure that you get a freshly delivered page! Or, try + using Shift+Reload. @@ -7955,19 +8150,21 @@ In file: user.action [ View ] [ Edit ] - That actually was very telling and pointed us quickly to where the problem + That actually was very helpful and pointed us quickly to where the problem was. If you don't get this kind of match, then it means one of the default - rules in the first section is causing the problem. This would require some - guesswork, and maybe a little trial and error to isolate the offending rule. - One likely cause would be one of the {+filter} actions. These - tend to be harder to troubleshoot. Try adding the URL for the site to one of - aliases that turn off +filter: + rules in the first section of default.action is causing + the problem. This would require some guesswork, and maybe a little trial and + error to isolate the offending rule. One likely cause would be one of the + +filter actions. + These tend to be harder to troubleshoot. + Try adding the URL for the site to one of aliases that turn off + +filter: - {shop} + { shop } .quietpc.com .worldpay.com # for quietpc.com .jungle.com @@ -7977,8 +8174,8 @@ In file: user.action [ View ] [ Edit ] - {shop} is an alias that expands to - { -filter -session-cookies-only }. + { shop } is an alias that expands to + { -filter -session-cookies-only }. Or you could do your own exception to negate filtering: @@ -7986,29 +8183,55 @@ In file: user.action [ View ] [ Edit ] - {-filter} + { -filter } + # Disable ALL filter actions for sites in this section .forbes.com + developer.ibm.com + localhost - This would turn off all filtering for that site. This would probably be most - appropriately put in user.action, for local site - exceptions. + This would turn off all filtering for these sites. This is best + put in 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. Images that are inexplicably being blocked, may well be hitting the - +filter{banners-by-size} rule, which assumes - that images of certain sizes are ad banners (works well most of the time - since these tend to be standardized). ++filter{banners-by-size} + rule, which assumes + that images of certain sizes are ad banners (works well + most of the time since these tend to be standardized). + + + + { fragile } is an alias that disables most + actions that are the most likely to cause trouble. This can be used as a + last resort for problem sites. + + + + + { fragile } + # Handle with care: easy to break + mail.google. + mybank.example.com + - {fragile} is an alias that disables most actions. This can be - used as a last resort for problem sites. Remember to flush caches! If this - still does not work, you will have to go through the remaining actions one by - one to find which one(s) is causing the problem. + Remember to flush caches! Note that the + mail.google reference lacks the TLD portion (e.g. + .com. This will effectively match any TLD with + google in it, such as mail.google.de, + just as an example. + + + If this still does not work, you will have to go through the remaining + actions one by one to find which one(s) is causing the problem. @@ -8037,6 +8260,9 @@ In file: user.action [ View ] [ Edit ]