X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fsource%2Fuser-manual.sgml;h=6a28302e0f99c9e4999067dc55b80bcd37df120e;hp=582af7fbd43bca5b47f46638cb10f3d9a717a508;hb=72081f829de368392d04076728f8c991178c0080;hpb=701f0d2c06084708ab71fe06ded88d4b666dc826 diff --git a/doc/source/user-manual.sgml b/doc/source/user-manual.sgml index 582af7fb..6a28302e 100644 --- a/doc/source/user-manual.sgml +++ b/doc/source/user-manual.sgml @@ -11,11 +11,11 @@ - - + + - + @@ -32,9 +32,9 @@ This file belongs into ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/ - $Id: user-manual.sgml,v 2.9 2003/04/11 03:14:53 hal9 Exp $ + $Id: user-manual.sgml,v 1.123.2.43 2005/05/23 09:59:10 hal9 Exp $ - Copyright (C) 2001, 2002 Privoxy Developers + Copyright (C) 2001- 2003 Privoxy Developers See LICENSE. ======================================================================== @@ -53,12 +53,12 @@ - Copyright &my-copy; 2001, 2002 by + Copyright &my-copy; 2001 - 2004 by Privoxy Developers -$Id: user-manual.sgml,v 2.9 2003/04/11 03:14:53 hal9 Exp $ +$Id: user-manual.sgml,v 1.123.2.43 2005/05/23 09:59:10 hal9 Exp $ @@ -125,10 +114,12 @@ Hal. This documentation is included with the current &p-status; version of Privoxy, v.&p-version;. + and is mostly complete at this point. The most up to date reference for the + time being is still the comments in the source files and in the individual + configuration files. Development of version 3.0 is currently nearing + completion, and includes many significant changes and enhancements over + earlier versions. The target release date for + stable v3.0 is soon ;-)]]>. @@ -137,7 +128,7 @@ Hal. Since this is a &p-status; version, not all new features are well tested. This documentation may be slightly out of sync as a result (especially with CVS sources). And there may be bugs, though hopefully - not many! Please find them! + not many! ]]> @@ -232,8 +223,7 @@ automatically start Privoxy in the boot process. Just double-click the installer, which will guide you through the installation process. You will find the configuration files - in the same directory as you installed Privoxy in. We do not - use the registry of Windows. + in the same directory as you installed Privoxy in. @@ -350,7 +340,7 @@ automatically start Privoxy in the boot process. possibly unstable development versions, you can check out the up-to-the-minute version directly from the CVS repository or simply download the nightly CVS + url="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.bz2">the nightly CVS tarball. @@ -377,7 +367,7 @@ automatically start Privoxy in the boot process. - In order not to loose your personal changes and adjustments when updating + In order not to lose your personal changes and adjustments when updating to the latest default.action file we strongly recommend that you use user.action for your customization of Privoxy. See the next section for a quick introduction to how Privoxy blocks ads and banners.]]> - + @@ -565,6 +555,14 @@ automatically start Privoxy in the boot process. + + + For easy access to Privoxy's most important controls, drag the provided + Bookmarklets into your browser's + personal toolbar. + + + Please see the section Contacting the @@ -1050,7 +1048,7 @@ Example Unix startup command: See the section Command line options for - furher info. + further info. must find a better place for this paragraph @@ -1204,7 +1202,20 @@ must find a better place for this paragraph USER, and if included the GID of GROUP. Exit if the privileges are not sufficient to do so. Unix only. - + + + + --chroot + + + + Before changing to the user ID given in the --user option, + chroot to that user's home directory, i.e. make the kernel pretend to the Privoxy + process that the directory tree starts there. If set up carefully, this can limit + the impact of possible vulnerabilities in Privoxy to the files contained in that hierarchy. + Unix only. + + configfile @@ -1444,9 +1455,9 @@ must find a better place for this paragraph Privoxy takes for which URLs, and thus determine how ad images, cookies and various other aspects of HTTP content and transactions are handled, and on which sites (or even parts thereof). There - are three such files included with Privoxy, with - differing purposes: - + are three such files included with Privoxy + with differing purposes: + @@ -1478,14 +1489,149 @@ must find a better place for this paragraph you select them explicitly in the editor. It is not recommend to edit this file. + + The default profiles, and their associated actions, as pre-defined in + standard.action are: + + + Default Configurations + + + + + + + + Feature + Cautious + Medium + Adventuresome + + + + + + + + + + + + + + Ad-blocking by URL + yes + yes + yes + + + + Ad-filtering by size + yes + yes + yes + + + + GIF de-animation + no + yes + yes + + + + Referer forging + no + yes + yes + + + + Cookie handling + none + session-only + kill + + + + Pop-up killing + unsolicited + unsolicited + all + + + + Fast redirects + no + no + yes + + + + HTML taming + yes + yes + yes + + + + JavaScript taming + yes + yes + yes + + + + Web-bug killing + yes + yes + yes + + + + Fun text replacements + no + no + yes + + + + Image tag reordering + no + no + yes + + + + Ad-filtering by link + no + no + yes + + + + Demoronizer + no + no + yes + + + + + +
+ + The list of actions files to be used are defined in the main configuration - file, and are processed in the order they are defined. The content of these - can all be viewed and edited from default.action is typically process before + user.action). The content of these can all be viewed and + edited from http://config.privoxy.org/show-status. @@ -1523,10 +1669,10 @@ must find a better place for this paragraph 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 make later. If, for example, you want to kill popup windows per + will have to make later. If, for example, you want to crunch all cookies per default, you'll have to make exceptions from that rule for sites that you - regularly use and that require popups for actually useful content, like maybe - your bank, favorite shop, or newspaper. + regularly use and that require cookies for actually useful puposes, like maybe + your bank, favorite shop, or newspaper. @@ -1546,8 +1692,8 @@ must find a better place for this paragraph 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 Radical. - Warning: the Radical setting is not only more aggressive, + 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! @@ -1573,7 +1719,7 @@ must find a better place for this paragraph To determine which actions apply to a request, the URL of the request is - compared to all patterns in each action file file. Every time it matches, the list of + compared to all patterns in each action file file. Every time it matches, the list of applicable actions for the URL is incrementally updated, using the heading of the section in which the pattern is located. If multiple matches for the same URL set the same action differently, the last match wins. If not, @@ -1682,7 +1828,7 @@ must find a better place for this paragraph matches any domain that ENDS in - .example.com (e.g. www.example.com) + .example.com @@ -2447,9 +2593,12 @@ problem-host.example.com Effect: - Text documents, including HTML and JavaScript, to which this action - applies, are filtered on-the-fly through the specified regular expression - based substitutions. + All files of text-based type, most notably HTML and JavaScript, to which this + action applies, are filtered on-the-fly through the specified regular expression + 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.) @@ -2469,8 +2618,8 @@ problem-host.example.com The name of a filter, as defined in the filter file (typically default.filter, set by the filterfile - option in the config file). Filtering - can be completely disabled without the use of parameters. + option in the config file). When used in its negative form, + and without parameters, filtering is completely disabled. @@ -2483,10 +2632,6 @@ problem-host.example.com in the distribution filter file that you can use. See the examples below for a list. - - This is potentially a very powerful feature! But rolling your own - filters requires a knowledge of regular expressions and HTML. - Filtering requires buffering the page content, which may appear to slow down page rendering since nothing is displayed until all content has @@ -2494,6 +2639,10 @@ problem-host.example.com since the page is not incrementally displayed.) This effect will be more noticeable on slower connections. + + This is very powerful feature, but rolling your own + filters requires a knowledge of regular expressions and HTML. + The amount of data that can be filtered is limited to the buffer-limit @@ -2502,9 +2651,12 @@ problem-host.example.com data, and all pending data, is passed through unfiltered. - Inappropriate MIME types, such as zipped files, are not filtered at all. - Encrypted SSL data (from HTTPS servers) cannot be filtered either since - this would violate the integrity of the secure transaction. + Inadequate 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. At this time, Privoxy cannot (yet!) uncompress compressed @@ -2525,75 +2677,99 @@ problem-host.example.com Feedback with suggestions for new or improved filters is particularly welcome! + + The below list has only the names and a one-line description of each + predefined filter. There are more + verbose explanations of what these filters do in the filter file chapter. + - Example usage (with filters from the distribution default.filter file): + Example usage (with filters from the distribution default.filter file). + See the Predefined Filters section for + more explanation on each: + + + +filter{js-annoyances} # Get rid of particularly annoying JavaScript abuse + + + + +filter{js-events} # Kill all JS event bindings (Radically destructive! Only for extra nasty sites) + - +filter{html-annoyances} # Get rid of particularly annoying HTML abuse. + +filter{html-annoyances} # Get rid of particularly annoying HTML abuse - - +filter{js-annoyances} # Get rid of particularly annoying JavaScript abuse + + +filter{content-cookies} # Kill cookies that come in the HTML or JS content - - +filter{banners-by-size} # Kill banners based on their size for this page (very efficient!) + + +filter{refresh-tags} # Kill automatic refresh tags (for dial-on-demand setups) - - +filter{banners-by-link} # Kill banners based on the link they are contained in (experimental) + + +filter{unsolicited-popups} # Disable only unsolicited pop-up windows + + + + +filter{all-popups} # Kill all popups in JavaScript and HTML +filter{img-reorder} # Reorder attributes in <img> tags to make the banners-by-* filters more effective - - +filter{content-cookies} # Kill cookies that come sneaking in the HTML or JS content + + +filter{banners-by-size} # Kill banners by size - - +filter{popups} # Kill all popups in JS and HTML + + +filter{banners-by-link} # Kill banners by their links to known clicktrackers +filter{webbugs} # Squish WebBugs (1x1 invisible GIFs used for user tracking) - - +filter{fun} # Text replacements for subversive browsing fun! + + +filter{tiny-textforms} # Extend those tiny textareas up to 40x80 and kill the hard wrap - - +filter{frameset-borders} # Give frames a border and make them resizeable + + +filter{jumping-windows} # Prevent windows from resizing and moving themselves - - +filter{refresh-tags} # Kill automatic refresh tags (for dial-on-demand setups) + + +filter{frameset-borders} # Give frames a border and make them resizable - - +filter{nimda} # Remove Nimda (virus) code. + + +filter{demoronizer} # Fix MS's non-standard use of standard charsets +filter{shockwave-flash} # Kill embedded Shockwave Flash objects - - +filter{crude-parental} # Kill all web pages that contain the words "sex" or "warez" + + +filter{quicktime-kioskmode} # Make Quicktime movies saveable - - +filter{js-events} # Kill all JS event bindings (Radically destructive! Only for extra nasty sites) + + +filter{fun} # Text replacements for subversive browsing fun! - - +filter{demoronizer} # Fix non-standard MS font extensions for non-MS browsers + + +filter{crude-parental} # Crude parental filtering (demo only) + + + + +filter{ie-exploits} # Disable some known Internet Explorer bug exploits @@ -2998,7 +3174,7 @@ ad.doubleclick.net Typical use: - Eliminate those annoying pop-up windows + Eliminate those annoying pop-up windows (deprecated) @@ -3033,13 +3209,15 @@ ad.doubleclick.net Notes: - This action is easily confused with the built-in, hardwired filter + This action is basically a built-in, hardwired special-purpose filter action, but there are important differences: For kill-popups, the document need not be buffered, so it can be incrementally rendered while downloading. But kill-popups doesn't catch as many pop-ups as filter{popups} - does. + linkend="FILTER-ALL-POPUPS">filter{all-popups} + does and is not as smart as filter{unsolicited-popups} + is. Think of it as a fast and efficient replacement for a filter that you @@ -3050,9 +3228,12 @@ ad.doubleclick.net the kill-popups action over its filter equivalent. - Killing all pop-ups is a dangerous business. Many shops and banks rely on - pop-ups to display forms, shopping carts etc, and killing only the unwanted pop-ups - would require artificial intelligence in Privoxy. + Killing all pop-ups unconditionally is problematic. Many shops and banks rely on + pop-ups to display forms, shopping carts etc, and the filter{unsolicited-popups} + does a fairly good job of catching only the unwanted ones. + + If the only kind of pop-ups that you want to kill are exit consoles (those really nasty windows that appear when you close an other one), you might want to use @@ -3391,7 +3572,8 @@ my-internal-testing-server.void Typical use: - Allow only temporary session cookies (for the current browser session only). + Allow only temporary session cookies (for the current + browser session only). @@ -3400,8 +3582,9 @@ my-internal-testing-server.void Effect: - Deletes the expires field from Set-Cookie: server headers. - Most browsers will not store such cookies permanently and forget them in between sessions. + Deletes the expires field from Set-Cookie: + server headers. Most browsers will not store such cookies permanently and + forget them in between sessions. @@ -3530,7 +3713,8 @@ my-internal-testing-server.void target-url to send a redirect to target-url. You can redirect - to any image anywhere, even in your local filesystem (via file:/// URL). + to any image anywhere, even in your local filesystem via file:/// URL. + (But note that not all browsers support redirecting to a local file system). A good application of redirects is to use special Privoxy-built-in @@ -3660,16 +3844,16 @@ my-internal-testing-server.void # These aliases just save typing later: # (Note that some already use other aliases!) # - +crunch-all-cookies = +crunch-incoming-cookies +crunch-outgoing-cookies - -crunch-all-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies + +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 - mercy-for-cookies = -crunch-all-cookies -session-cookies-only + mercy-for-cookies = -crunch-all-cookies -session-cookies-only -filter{content-cookies} # These aliases define combinations of actions # that are useful for certain types of sites: # - fragile = -block -crunch-all-cookies -filter -fast-redirects -hide-referer -kill-popups - shop = -crunch-all-cookies -filter{popups} -kill-popups + fragile = -block -filter -crunch-all-cookies -fast-redirects -hide-referrer -kill-popups + shop = -crunch-all-cookies -filter{all-popups} -kill-popups # Short names for other aliases, for really lazy people ;-) # @@ -3703,7 +3887,7 @@ my-internal-testing-server.void # These shops require pop-ups: # - {shop -kill-popups -filter{popups}} + {shop -kill-popups -filter{all-popups}} .dabs.com .overclockers.co.uk @@ -3767,19 +3951,19 @@ that also explains why and how aliases are used: ########################################################################## {{alias}} -# These aliases just save typing later: -# (Note that some already use other aliases!) -# -+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 -mercy-for-cookies = -crunch-all-cookies -session-cookies-only + # These aliases just save typing later: + # (Note that some already use other aliases!) + # + +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 + mercy-for-cookies = -crunch-all-cookies -session-cookies-only -filter{content-cookies} -# These aliases define combinations of actions -# that are useful for certain types of sites: -# -fragile = -block -crunch-all-cookies -filter -fast-redirects -hide-referer -kill-popups -shop = mercy-for-cookies -filter{popups} -kill-popups + # These aliases define combinations of actions + # that are useful for certain types of sites: + # + fragile = -block -filter -crunch-all-cookies -fast-redirects -hide-referrer -kill-popups + shop = -crunch-all-cookies -filter{all-popups} -kill-popups @@ -3822,20 +4006,26 @@ shop = mercy-for-cookies -filter{popups} -kill-popups +deanimate-gifs \ -downgrade-http-version \ +fast-redirects \ - +filter{html-annoyances} \ +filter{js-annoyances} \ + -filter{js-events} \ + +filter{html-annoyances} \ -filter{content-cookies} \ - +filter{popups} \ - +filter{webbugs} \ - -filter{refresh-tags} \ - -filter{fun} \ - +filter{nimda} \ + +filter{refresh-tags} \ + +filter{unsolicited-popups} \ + -filter{all-popups} \ + +filter{img-reorder} \ +filter{banners-by-size} \ -filter{banners-by-link} \ - -filter{img-reorder} \ + +filter{webbugs} \ + -filter{tiny-textforms} \ + +filter{jumping-windows} \ + -filter{frameset-borders} \ + -filter{demoronizer} \ -filter{shockwave-flash} \ + -filter{quicktime-kioskmode} \ + -filter{fun} \ -filter{crude-parental} \ - -filter{js-events} \ + +filter{ie-exploits} \ -handle-as-image \ +hide-forwarded-for-headers \ +hide-from-header{block} \ @@ -3859,8 +4049,6 @@ shop = mercy-for-cookies -filter{popups} -kill-popups like not blocking (which is understandably the default!) need exceptions, i.e. we need to specify explicitly what we want to block in later sections. - We will also want to make exceptions from our general pop-up-killing, - and use our defined aliases for that. @@ -3902,13 +4090,15 @@ shop = mercy-for-cookies -filter{popups} -kill-popups .scan.co.uk + + The fast-redirects action, which we enabled per default above, breaks some sites. So disable @@ -4115,6 +4307,7 @@ www.ugu.com/sui/ugu/adv user.action + So far we are painting with a broad brush by setting general policies, which would be a reasonable starting point for many people. Now, @@ -4162,14 +4355,14 @@ www.ugu.com/sui/ugu/adv +crunch-all-cookies = +crunch-incoming-cookies +crunch-outgoing-cookies -crunch-all-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies allow-all-cookies = -crunch-all-cookies -session-cookies-only - allow-popups = -filter{popups} -kill-popups + allow-popups = -filter{all-popups} -kill-popups +block-as-image = +block +handle-as-image -block-as-image = -block # These aliases define combinations of actions that are useful for # certain types of sites: # -fragile = -block -crunch-all-cookies -filter -fast-redirects -hide-referer -kill-popups +fragile = -block -crunch-all-cookies -filter -fast-redirects -hide-referrer -kill-popups shop = -crunch-all-cookies allow-popups # Allow ads for selected useful free sites: @@ -4191,43 +4384,40 @@ allow-ads = -block -filter{banners-by-size} -filter{banners-by-link} { allow-all-cookies } +sourceforge.net sunsolve.sun.com -slashdot.org +.slashdot.org .yahoo.com .msdn.microsoft.com .redhat.com - Your bank needs popups and is allergic to some filter, but you don't - know which, so you disable them all: + Your bank is allergic to some filter, but you don't know which, so you disable them all: -{ -filter -kill-popups } +{ -filter } .your-home-banking-site.com - Some hosts and some file types you may not want to filter. - Privoxy makes no distinctions between regular web - pages and downloads done via your web browser if it is an html or text type - document. + Some file types you may not want to filter for various reasons: -{ -filter } -localhost -apache_server.mylan - -# A list of common file extensions that are likely to indicate raw text, and best -# if unfiltered. -/(.*/)?.*\.(pl|(s|p)?h|c(c|xx|pp)?|tcl|am|init?|cfg?|conf(ig)?|txt|rc|bat)$ +# Technical documentation is likely to contain strings that might +# erroneously get altered by the JavaScript-oriented filters: +# +.tldp.org +/(.*/)?selfhtml/ -# Documentation should not need filtering (at least on some sites). -.tldp.org +# And this stupid host sends streaming video with a wrong MIME type, +# so that Privoxy thinks it is getting HTML and starts filtering: +# +stupid-server.example.com/ @@ -4245,30 +4435,27 @@ apache_server.mylan { +block } www.example.com/nasty-ads/sponsor.gif -another.popular.site.net/more/junk/here/ - -# Here we found one that is not in Privoxy's default blocked list: -.adfactory.net +another.popular.site.net/more/junk/here/ - To force URLs that tend to have ad images, but it is difficult for - Privoxy to know this since the ultimate returned - object is obscured for one reason or another, we can try to force these to be - treated as images (and thus avoid Privoxy's - BLOCKED banner page). Note that if what is returned by the - server turns out NOT to be an image, then your browser typically will display - a broken icon image. Use cautiously. + The URLs of dynamically generated banners, especially from large banner + farms, often don't use the well-known image file name extensions, which + makes it impossible for Privoxy to guess + the file type just by looking at the URL. + You can use the +block-as-image alias defined above for + these cases. + Note that objects which match this rule but then turn out NOT to be an + image are typically rendered as a broken image icon by the + browser. Use cautiously. { +block-as-image } -# A shockwave ad, very annoying. -.trip.com/.*\.swf .doubleclick.net /Realmedia/ads/ -adremote. +ar.atwola.com/ @@ -4381,11 +4568,11 @@ adremote. - Filtering works on any text-based document type, including plain - text, HTML, JavaScript, CSS etc. (all text/* - MIME types). Substitutions are made at the source level, so if - you want to roll your own filters, you should be - familiar with HTML syntax. + Filtering works on any text-based document type, including + HTML, JavaScript, CSS etc. (all text/* + MIME types, except text/plain). + Substitutions are made at the source level, so if you want to roll + your own filters, you should be familiar with HTML syntax. @@ -4442,6 +4629,7 @@ adremote. The below examples might also help to get you started. + Filter File Tutorial @@ -4668,6 +4856,349 @@ s* industry[ -]leading \ You get the idea? + + + + +The Pre-defined Filters + + + + +The distribution default.filter file contains a selection of +pre-defined filters for your convenience: + + + + + js-annoyances + + + The purpose of this filter is to get rid of particularly annoying JavaScript abuse. + To that end, it + + + + replaces JavaScript references to the browser's referrer information + with the string "Not Your Business!". This compliments the hide-referrer action on the content level. + + + + + removes the bindings to the DOM's + unload + event which we feel has no right to exist and is responsible for most exit consoles, i.e. + nasty windows that pop up when you close another one. + + + + + removes code that causes new windows to be opened with undesired properties, such as being + full-screen, non-resizable, without location, status or menu bar etc. + + + + + + + + + js-events + + + This is a very radical measure. It removes virtually all JavaScript event bindings, which + means that scripts can not react to user actions such as mouse movements or clicks, window + resizing etc, anymore. + + + We strongly discourage using this filter as a default since it breaks + many legitimate scripts. It is meant for use only on extra-nasty sites (should you really + need to go there). + + + + + + html-annoyances + + + This filter will undo many common instances of HTML based abuse. + + + The BLINK and MARQUEE tags + are neutralized (yeah baby!), and browser windows will be created as + resizable (as of course they should be!), and will have location, + scroll and menu bars -- even if specified otherwise. + + + + + + content-cookies + + + Most cookies are set in the HTTP dialogue, where they can be intercepted + by the + crunch-incoming-cookies + and crunch-outgoing-cookies + actions. But web sites increasingly make use of HTML meta tags and JavaScript + to sneak cookies to the browser on the content level. + + + This filter disables HTML and JavaScript code that reads or sets cookies. Use + it wherever you would also use the cookie crunch actions. + + + + + + refresh tags + + + Disable any refresh tags if the interval is greater than nine seconds (so + that redirections done via refresh tags are not destroyed). This is useful + for dial-on-demand setups, or for those who find this HTML feature + annoying. + + + + + + unsolicited-popups + + + This filter attempts to prevent only unsolicited pop-up + windows from opening, yet still allow pop-up windows that the user + has explicitly chosen to open. It was added in version 3.0.1, + as an improvement over earlier such filters. + + + Technical note: The filter works by redefining the window.open JavaScript + function to a dummy function during the loading and rendering phase of each + HTML page access, and restoring the function afterwards. + + + + + + all-popups + + + Attempt to prevent all pop-up windows from opening. + Note this should be used with more discretion than the above, since it is + more likely to break some sites that require pop-ups for normal usage. Use + with caution. + + + + + + img-reorder + + + This is a helper filter that has no value if used alone. It makes the + banners-by-size and banners-by-link + (see below) filters more effective and should be enabled together with them. + + + + + + banners-by-size + + + This filter removes image tags purely based on what size they are. Fortunately + for us, many ads and banner images tend to conform to certain standardized + sizes, which makes this filter quite effective for ad stripping purposes. + + + Occasionally this filter will cause false positives on images that are not ads, + but just happen to be of one of the standard banner sizes. + + + + + + banners-by-link + + + This is an experimental filter that attempts to kill any banners if + their URLs seem to point to known or suspected click trackers. It is currently + not of much value and is not recommended for use by default. + + + + + + webbugs + + + Webbugs are small, invisible images (technically 1X1 GIF images), that + are used to track users across websites, and collect information on them. + As an HTML page is loaded by the browser, an embedded image tag causes the + browser to contact a third-party site, disclosing the tracking information + through the requested URL and/or cookies for that third-party domain, without + the use ever becoming aware of the interaction with the third-party site. + HTML-ized spam also uses a similar technique to verify email addresses. + + + This filter removes the HTML code that loads such webbugs. + + + + + + tiny-textforms + + + A rather special-purpose filter that can be used to enlarge textareas (those + multi-line text boxes in web forms) and turn off hard word wrap in them. + It was written for the sourceforge.net tracker system where such boxes are + a nuisance, but it can be handy on other sites, too. + + + It is not recommended to use this filter as a default. + + + + + + jumping-windows + + + Many consider windows that move, or resize themselves to be abusive. This filter + neutralizes the related JavaScript code. Note that some sites might not display + or behave as intended when using this filter. + + + + + + frameset-borders + + + Some web designers seem to assume that everyone in the world will view their + web sites using the same browser brand and version, screen resolution etc, + because only that assumption could explain why they'd use static frame sizes, + yet prevent their frames from being resized by the user, should they be too + small to show their whole content. + + + This filter removes the related HTML code. It should only be applied to sites + which need it. + + + + + + demoronizer + + + Many Microsoft products that generate HTML use non-standard extensions (read: + violations) of the ISO 8859-1 aka Latin-1 character set. This causes those + HTML documents to display with errors on standard-compliant platforms. + + + This filter translates the MS-only characters into Latin-1 equivalents. + It is not necessary when using MS products, and will cause corruption of + all documents that use 8-bit character sets other than Latin-1. It's mostly + worthwhile for Europeans on non-MS platforms, if wierd garbage characters + sometimes appear on some pages. + + + + + + shockwave-flash + + + A filter for shockwave haters. As the name suggests, this filter strips code + out of web pages that is used to embed shockwave flash objects. + + + + + + + + quicktime-kioskmode + + + Change HTML code that embeds Quicktime objects so that kioskmode, which + prevents saving, is disabled. + + + + + + fun + + + Text replacements for subversive browsing fun. Make fun of your favorite + Monopolist or play buzzword bingo. + + + + + + crude-parental + + + A demonstration-only filter that shows how Privoxy + can be used to delete web content on a keyword basis. + + + + + + ie-exploits + + + A collection of text replacements to disable malicious HTML and JavaScript + code that exploits known security holes in Internet Explorer. + + + Presently, it only protects against Nimda and a cross-site scripting bug, and + would need active maintenance to provide more substantial protection. + + + + + + site-specifics + + + Some web sites have very specific problems, the cure for which doesn't apply + anywhere else, or could even cause damage on other sites. + + + This is a collection of such site-specific cures which should only be applied + to the sites they were intended for, which is what the supplied + default.action file does. Users shouldn't need to change + anything regarding this filter. + + + + + + + @@ -4720,7 +5251,7 @@ s* industry[ -]leading \ blocks of HTML code disappear when a specific symbol is set. We use this for many purposes, one of them being to include the beta warning in all our user interface (CGI) pages when Privoxy - in in an alpha or beta development stage: + is in an alpha or beta development stage: @@ -5764,32 +6295,88 @@ In file: user.action [ View ] [ Edit ]