From be4b22d1ab5a793668d34f583f52cc867632ccc4 Mon Sep 17 00:00:00 2001 From: hal9 Date: Sun, 28 Apr 2002 05:43:59 +0000 Subject: [PATCH] This is the break up of configuration.html into multiple files. This will probably break links elsewhere :( --- doc/source/user-manual.sgml | 497 +++++++++++++++++++----------------- 1 file changed, 260 insertions(+), 237 deletions(-) diff --git a/doc/source/user-manual.sgml b/doc/source/user-manual.sgml index b73373eb..e92a15f4 100644 --- a/doc/source/user-manual.sgml +++ b/doc/source/user-manual.sgml @@ -25,7 +25,7 @@ This file belongs into ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/ - $Id: user-manual.sgml,v 1.96 2002/04/27 05:32:00 hal9 Exp $ + $Id: user-manual.sgml,v 1.97 2002/04/27 21:04:42 hal9 Exp $ Written by and Copyright (C) 2001 the SourceForge Privoxy team. http://www.privoxy.org/ @@ -46,7 +46,7 @@ Privoxy User Manual -$Id: user-manual.sgml,v 1.96 2002/04/27 05:32:00 hal9 Exp $ +$Id: user-manual.sgml,v 1.97 2002/04/27 21:04:42 hal9 Exp $ @@ -308,15 +308,15 @@ automatically start Privoxy in the boot process. configuration files will not migrate. The functionality of the old blockfile, cookiefile and imagelist, are now combined into the - actions files. default.action, - is the main actions file. Local exceptions should best be put into - user.action. + actions files. + default.action, is the main actions file. Local + exceptions should best be put into user.action. - A filter file (typically default.filter) - is new as of Privoxy 2.9.x, and provides some - of the new sophistication (explained below). config is - much the same as before. + A filter file (typically + default.filter) is new as of Privoxy + 2.9.x, and provides some of the new sophistication (explained + below). config is much the same as before. If upgrading from a 2.0.x version, you will have to use the new config @@ -359,9 +359,9 @@ automatically start Privoxy in the boot process. The primary configuration file for cookie management, ad and banner blocking, and many other aspects of Privoxy - configuration is in the actions files. It is strongly - recommended to become familiar with the new actions concept below, - before modifying these files. Locally defined rules + configuration is in the actions + files. It is strongly recommended to become familiar with the new + actions concept below, before modifying these files. Locally defined rules should go into user.action. @@ -488,10 +488,10 @@ automatically start Privoxy in the boot process. The included default configuration files should give a reasonable starting point. Most of the per site configuration is done in the - actions files. These are where various cookie actions are - defined, ad and banner blocking, and other aspects of - Privoxy configuration. There are several such - files included, with varying levels of aggressiveness. + actions files. These are + where various cookie actions are defined, ad and banner blocking, and other + aspects of Privoxy configuration. There are several + such files included, with varying levels of aggressiveness. @@ -508,9 +508,12 @@ automatically start Privoxy in the boot process. Another feature where you will probably want to define exceptions for trusted - sites is the popup-killing (through the +popup and - +filter{popups} actions), because your favorite shopping, - banking, or leisure site may need popups (explained below). + sites is the popup-killing (through the +kill-popupsand + +filter{popups} + actions), because your favorite shopping, banking, or leisure site may need + popups (explained below). @@ -559,7 +562,7 @@ automatically start Privoxy in the boot process. If the above paragraph sounds gibberish to you, you might want to read more about the actions concept + url="actions-file.html#ACTIONSFILE">read more about the actions concept or even dive deep into the Appendix on actions. @@ -832,13 +835,17 @@ automatically start Privoxy in the boot process. please check all your configuration files on important issues. ]]> + + + - + - + The Main Configuration File + Again, the main configuration file is named config on Linux/Unix/BSD and OS/2, and config.txt on Windows. @@ -878,7 +885,7 @@ automatically start Privoxy in the boot process. - + Configuration and Log File Locations @@ -889,7 +896,7 @@ automatically start Privoxy in the boot process. -confdir +confdir @@ -932,10 +939,10 @@ automatically start Privoxy in the boot process. - + -logdir +logdir @@ -974,15 +981,15 @@ automatically start Privoxy in the boot process. - + - +<sect3 renderas="sect4" id="actionsfile"><title> actionsfile - + Specifies: @@ -1026,7 +1033,7 @@ actionsfile Notes: - Multiple actionsfile lines are OK and are in fact recommended! + Multiple actionsfile lines are permitted, and are in fact recommended! The default values include standard.action, which is used for internal @@ -1035,14 +1042,17 @@ actionsfile user.action, where you can make your personal additions. - There is no point in using Privoxy without an actions file. + Actions files are where all the per site and per URL configuration is done for + ad blocking, cookie management, privacy considerations, etc. + There is no point in using Privoxy without at + least one actions file. - + -filterfile +filterfile @@ -1089,9 +1099,9 @@ actionsfile - + -logfile +logfile @@ -1150,9 +1160,9 @@ actionsfile - + -jarfile +jarfile @@ -1192,9 +1202,9 @@ actionsfile - + -trustfile +trustfile Specifies: @@ -1246,9 +1256,9 @@ actionsfile - + -user-manual +user-manual Specifies: @@ -1295,17 +1305,17 @@ actionsfile - - + + - + Local Set-up Documentation @@ -1314,7 +1324,7 @@ actionsfile you, what you block and why you do that, your policies etc. -trust-info-url +trust-info-url @@ -1364,9 +1374,9 @@ actionsfile - + -admin-address +admin-address @@ -1408,9 +1418,9 @@ actionsfile - + -proxy-info-url +proxy-info-url @@ -1456,14 +1466,14 @@ actionsfile - - + + - + Debugging @@ -1473,7 +1483,7 @@ actionsfile command line option when debugging. -debug +debug @@ -1550,9 +1560,9 @@ actionsfile - + -single-threaded +single-threaded @@ -1594,13 +1604,13 @@ actionsfile - - + + - + Access Control and Security @@ -1608,7 +1618,7 @@ actionsfile of Privoxy's configuration. -listen-address +listen-address @@ -1626,6 +1636,7 @@ actionsfile [IP-Address]:Port + Default value: @@ -1678,9 +1689,9 @@ actionsfile - + -toggle +toggle @@ -1720,7 +1731,7 @@ actionsfile proxy. See enable-remote-toggle below. This is not really useful anymore, since toggling is much easier via the web - interface then via editing the conf file. + interface than via editing the conf file. The windows version will only display the toggle icon in the system tray @@ -1729,10 +1740,10 @@ actionsfile - + -enable-remote-toggle +enable-remote-toggle Specifies: @@ -1786,10 +1797,10 @@ actionsfile - + -enable-edit-actions +enable-edit-actions Specifies: @@ -1838,9 +1849,9 @@ actionsfile - + - +<sect3 renderas="sect4" id="acls"><title> ACLs: permit-access and deny-access @@ -1963,9 +1974,9 @@ ACLs: permit-access and deny-access - + -buffer-limit +buffer-limit @@ -2018,16 +2029,16 @@ ACLs: permit-access and deny-access - - + + - + Forwarding @@ -2047,7 +2058,7 @@ ACLs: permit-access and deny-access supports the SOCKS 4 and SOCKS 4A protocols. -forward +forward Specifies: @@ -2126,9 +2137,9 @@ ACLs: permit-access and deny-access - + - +<sect3 renderas="sect4" id="socks"><title> forward-socks4 and forward-socks4a @@ -2218,9 +2229,9 @@ forward-socks4 and forward-socks4a - + -Advanced Forwarding Examples +Advanced Forwarding Examples If you have links to multiple ISPs that provide various special content @@ -2294,16 +2305,16 @@ forward-socks4 and forward-socks4a Squid normally uses port 3128. If unsure consult http_port in squid.conf. - - + + - + Windows GUI Options Privoxy has a number of options specific to the @@ -2475,20 +2486,22 @@ forward-socks4 and forward-socks4a - #hide-console + #hide-console - + - -Actions Files + + + +Actions Files The actions files are used to define what actions @@ -2516,18 +2529,18 @@ forward-socks4 and forward-socks4a An actions file typically has sections. Near the top, aliases are optionally defined (discussed below), then the default set of rules + url="actions-file.html#ALIASES">below), then the default set of rules which will apply universally to all sites and pages. And then below that, exceptions to the defined universal policies. - + Finding the Right Mix - Note that some actions like cookie suppression - or script disabling may render some sites unusable, which rely on these - techniques to work properly. Finding the right mix of actions is not easy and + 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 aggressive your default settings (in the top section of the actions file) are, the more exceptions for trusted sites you @@ -2543,10 +2556,10 @@ forward-socks4 and forward-socks4a things. There just are too many variables, and sites are constantly changing. Sooner or later you will want to change the rules (and read this chapter again :). - + - + How to Edit The easiest way to edit the actions files is with a browser by @@ -2558,10 +2571,10 @@ forward-socks4 and forward-socks4a If you prefer plain text editing to GUIs, you can of course also directly edit the the actions files. - + - + How Actions are Applied to URLs Actions files are divided into sections. There are special sections, @@ -2579,8 +2592,8 @@ forward-socks4 and forward-socks4a 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, the effects are aggregated (e.g. a URL might match both the - +handle-as-image - and +block actions). + +handle-as-image + and +block actions). @@ -2593,10 +2606,10 @@ forward-socks4 and forward-socks4a More detail on this is provided in the Appendix, Anatomy of an Action. - + - + Patterns Generally, a pattern has the form <domain>/<path>, @@ -2652,7 +2665,9 @@ forward-socks4 and forward-socks4a -The Domain Pattern + + +The Domain Pattern The matching of the domain part offers some flexible options: if the @@ -2738,9 +2753,13 @@ forward-socks4 and forward-socks4a - + + + -The Path Pattern + + +The Path Pattern Privoxy uses Perl compatible regular expressions @@ -2772,16 +2791,16 @@ forward-socks4 and forward-socks4a documents whose path starts with PaTtErN in exactly this capitalization. - - + + - + Actions All actions are disabled by default, until they are explicitly enabled @@ -2894,7 +2913,7 @@ forward-socks4 and forward-socks4a - + <emphasis>+add-header</emphasis> @@ -2946,11 +2965,11 @@ forward-socks4 and forward-socks4a - + - + <emphasis>+block</emphasis> @@ -3009,15 +3028,15 @@ forward-socks4 and forward-socks4a A very important exception is if the URL matches both +block and +handle-as-image, + url="actions-file.html#HANDLE-AS-IMAGE">+handle-as-image, then it will be handled by - +set-image-blocker + +set-image-blocker (see below). It is important to understand this process, in order to understand how Privoxy is able to deal with ads and other objectionable content. - The +filter + The +filter action can also perform some of the same functionality as +block, but by virtue of very different programming techniques, and is most often used for different @@ -3027,11 +3046,11 @@ forward-socks4 and forward-socks4a - + - + <emphasis>+deanimate-gifs</emphasis> @@ -3087,10 +3106,10 @@ forward-socks4 and forward-socks4a - + - + <emphasis>+downgrade-http-version</emphasis> @@ -3144,10 +3163,10 @@ forward-socks4 and forward-socks4a - + - + <emphasis>+fast-redirects</emphasis> @@ -3217,11 +3236,11 @@ forward-socks4 and forward-socks4a - + - + <emphasis>+filter</emphasis> @@ -3351,7 +3370,7 @@ forward-socks4 and forward-socks4a Filtering can achieve some of the effects as the - +block + +block action, i.e. it can be used to block ads and banners. In the overall scheme of things, filtering is one of the first things Privoxy does with a web page. So other most other actions are applied to the @@ -3361,11 +3380,11 @@ forward-socks4 and forward-socks4a - + - + <emphasis>+hide-forwarded-for-headers</emphasis> @@ -3415,11 +3434,11 @@ forward-socks4 and forward-socks4a - + - + <emphasis>+hide-from-header</emphasis> @@ -3466,7 +3485,7 @@ forward-socks4 and forward-socks4a The keyword block will completely remove the header (not to be confused with the +block action). + url="actions-file.html#BLOCK">+block action). Alternately, you can specify any value you prefer to send to the web server. @@ -3474,11 +3493,11 @@ forward-socks4 and forward-socks4a - + - + <emphasis>+hide-referer</emphasis> @@ -3539,11 +3558,11 @@ forward-socks4 and forward-socks4a - + - + <emphasis>+hide-user-agent</emphasis> @@ -3596,10 +3615,10 @@ forward-socks4 and forward-socks4a - + - + <emphasis>+handle-as-image</emphasis> @@ -3649,10 +3668,10 @@ forward-socks4 and forward-socks4a +blocked, in which case a user definable image can be sent rather than a HTML page. This is integral to the whole concept of ad blocking: the URL must match both a +block rule, + url="actions-file.html#BLOCK">+block rule, and +handle-as-image. (See +set-image-blocker + url="actions-file.html#SET-IMAGE-BLOCKER">+set-image-blocker below for control over what will actually be displayed by the browser.) @@ -3662,11 +3681,11 @@ forward-socks4 and forward-socks4a - + - + <emphasis>+set-image-blocker</emphasis> @@ -3683,9 +3702,9 @@ forward-socks4 and forward-socks4a Decide what to do with URLs that end up tagged with both - +block + +block and +handle-as-image, + url="actions-file.html#HANDLE-AS-IMAGE">+handle-as-image, e.g an advertisement. @@ -3737,10 +3756,10 @@ forward-socks4 and forward-socks4a - + - + <emphasis>+limit-connect</emphasis> @@ -3812,10 +3831,10 @@ forward-socks4 and forward-socks4a - + - + <emphasis>+prevent-compression</emphasis> @@ -3861,10 +3880,10 @@ forward-socks4 and forward-socks4a Some websites do this, which can be a problem for Privoxy, since - +filter, - +kill-popups + +filter, + +kill-popups and +gif-deanimate + url="actions-file.html#GIF-DEANIMATE">+gif-deanimate will not work on compressed data. This will slow down connections to those websites, though. Default typically is to turn prevent-compression on. @@ -3873,10 +3892,10 @@ forward-socks4 and forward-socks4a - + - + <emphasis>+session-cookies-only</emphasis> @@ -3936,11 +3955,11 @@ forward-socks4 and forward-socks4a - + - + <emphasis>+prevent-reading-cookies</emphasis> @@ -3987,7 +4006,7 @@ forward-socks4 and forward-socks4a Often used in conjunction with +prevent-setting-cookies to disable cookies completely. Note that - +session-cookies-only + +session-cookies-only requires these to both be disabled (or else it never gets any cookies to cache). @@ -3999,11 +4018,11 @@ forward-socks4 and forward-socks4a - + - + <emphasis>+prevent-setting-cookies</emphasis> @@ -4055,11 +4074,11 @@ forward-socks4 and forward-socks4a - + - - + + <emphasis>+kill-popups<anchor id="kill-popups"></emphasis> @@ -4118,11 +4137,11 @@ forward-socks4 and forward-socks4a - + - + <emphasis>+send-vanilla-wafer</emphasis> @@ -4175,11 +4194,11 @@ forward-socks4 and forward-socks4a - + - + <emphasis>+send-wafer</emphasis> @@ -4230,11 +4249,11 @@ forward-socks4 and forward-socks4a - + - + Summary Note that many of these actions have the potential to cause a page to @@ -4245,11 +4264,11 @@ forward-socks4 and forward-socks4a linkend="ACTIONSANAT">Appendix for a brief example on troubleshooting actions. - + - + Sample Actions Files Remember that the meaning of any of the above references is reversed by preceding @@ -4288,7 +4307,7 @@ for-privoxy-version=3.0 ########################################################################## -# Aliases must be defined *before* they are used. These are +# Aliases must be defined *before* they are used. These are # easier to remember, and can combine several actions into one. Once # defined they can be used just like any built-in action -- but within # this file only! Aliases do not require a + or - sign. @@ -4321,36 +4340,36 @@ for-privoxy-version=3.0 # (unless an alias has been defined without this). ########################################################################## { \ - -add-header \ - -block \ - -deanimate-gifs \ - -downgrade-http-version \ - +fast-redirects \ - +filter{html-annoyances} \ - +filter{js-annoyances} \ - -filter{content-cookies} \ - -filter{popups} \ - +filter{webbugs} \ - -filter{refresh-tags} \ - -filter{fun} \ - +filter{nimda} \ - +filter{banners-by-size} \ - -filter{shockwave-flash} \ - -filter{crude-prental} \ - +hide-forwarded-for-headers \ - +hide-from-header{block} \ - -hide-referrer \ - -hide-user-agent \ - -handle-as-image \ - +set-image-blocker{pattern} \ - -limit-connect \ - +prevent-compression \ - -session-cookies-only \ - -prevent-reading-cookies \ - -prevent-setting-cookies \ - -kill-popups \ - -send-vanilla-wafer \ - -send-wafer \ + -add-header \ + -block \ + -deanimate-gifs \ + -downgrade-http-version \ + +fast-redirects \ + +filter{html-annoyances} \ + +filter{js-annoyances} \ + -filter{content-cookies} \ + -filter{popups} \ + +filter{webbugs} \ + -filter{refresh-tags} \ + -filter{fun} \ + +filter{nimda} \ + +filter{banners-by-size} \ + -filter{shockwave-flash} \ + -filter{crude-prental} \ + +hide-forwarded-for-headers \ + +hide-from-header{block} \ + -hide-referrer \ + -hide-user-agent \ + -handle-as-image \ + +set-image-blocker{pattern} \ + -limit-connect \ + +prevent-compression \ + -session-cookies-only \ + -prevent-reading-cookies \ + -prevent-setting-cookies \ + -kill-popups \ + -send-vanilla-wafer \ + -send-wafer \ } / # forward slash will match *all* potential URL patterns. @@ -4378,14 +4397,14 @@ for-privoxy-version=3.0 # These sites require pop-ups too :( We'll combine our 'shop' # alias with two other actions into one rule to allow all popups. - { shop -kill-popups -filter{popups} } + { shop -kill-popups -filter{popups} } .dabs.com .overclockers.co.uk # The 'Fast-redirects' action breaks some sites. Disable this action # for these known sensitive sites: - { -fast-redirects } + { -fast-redirects } login.yahoo.com edit.europe.yahoo.com .google.com @@ -4396,7 +4415,7 @@ for-privoxy-version=3.0 # Define which file types will be treated as images. Important # for ad blocking. - { +handle-as-image } + { +handle-as-image } /.*\.(gif|jpe?g|png|bmp|ico) @@ -4404,7 +4423,7 @@ for-privoxy-version=3.0 # our alias that we use here will block these as well as force # them to be treated as images. This combination of actions is # important for ad blocking. What the browser will show instead is -# determined by the setting of +set-image-blocker +# determined by the setting of +set-image-blocker { +imageblock } ar.atwola.com .ad.doubleclick.net @@ -4419,7 +4438,7 @@ for-privoxy-version=3.0 # These will just simply be blocked. They will generate the BLOCKED # banner page, if matched. Heavy use of wildcards and regular # expressions in this example. Enable block action: - { +block } + { +block } ad*. .*ads. banner?. @@ -4433,7 +4452,7 @@ for-privoxy-version=3.0 # sites we DO NOT want blocked via the wildcards and regular expressions. # Now let's set exceptions to the exceptions so the good guys get better # treatment. Disable block action: - { -block } + { -block } advogato.org adsl. ad[ud]*. @@ -4452,7 +4471,7 @@ for-privoxy-version=3.0 # Notice we don't have to name the individual filter # identifiers -- we just turn them all off in one fell swoop. # Disable all filters for this one site: - { -filter } + { -filter } .sourceforge.net @@ -4506,17 +4525,17 @@ for-privoxy-version=3.0 # My ISP uses obnoxious self promoting images on many pages. -# Nuke them :) Note that +handle-as-image need not be specified, +# Nuke them :) Note that +handle-as-image need not be specified, # since all URLs ending in .gif will be tagged as images by the # general rules in default.action anyway. - { +block } + { +block } www.my-isp-example.com/logo[0-9].gif # Say the site where you do your homebanking needs to open # popup windows, but you have chosen to kill popups by # default. This will allow it for your-example-bank.com: # - { -filter{popups} -kill-popups } + { -filter{popups} -kill-popups } .my-example-bank.com # This site is delicate, and requires kid-glove @@ -4528,14 +4547,14 @@ for-privoxy-version=3.0 - + - + Aliases Custom actions, known to Privoxy @@ -4618,14 +4637,16 @@ for-privoxy-version=3.0 - + - - + + + + The Filter File Any web page can be dynamically modified with the filter file. This @@ -4727,11 +4748,11 @@ for-privoxy-version=3.0 - -The +filter Action + +The <emphasis>+filter</emphasis> Action Filters are enabled with the +filter action from within + url="actions-file.html#FILTER">+filter action from within one of the actions files. +filter requires one parameter, which should match one of the section identifiers in the filter file itself. Example: @@ -4747,17 +4768,17 @@ for-privoxy-version=3.0 default, unless they are explicity enabled in one of the actions files. - - + + - + Templates When Privoxy displays one of its internal @@ -4777,8 +4798,6 @@ for-privoxy-version=3.0 may be customized or replaced with something else if desired. - - @@ -5293,13 +5312,13 @@ Requests Next, Privoxy checks to see if the URL matches any +block patterns. If + url="actions-file.html#BLOCK">+block patterns. If so, the URL is then blocked, and the remote web server will not be contacted. - +handle-as-image + +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 + url="actions-file.html#SET-IMAGE-BLOCKER">+set-image-blocker (blank, checkerboard pattern, or an HTTP redirect to an image elsewhere). @@ -5312,7 +5331,7 @@ Requests If the URL pattern matches the +fast-redirects action, + url="actions-file.html#FAST-REDIRECTS">+fast-redirects action, it is then processed. Unwanted parts of the requested URL are stripped. @@ -5320,7 +5339,7 @@ Requests Now the rest of the client browser's request headers are processed. If any of these match any of the relevant actions (e.g. +hide-user-agent, + url="actions-file.html#HIDE-USER-AGENT">+hide-user-agent, etc.), headers are suppressed or forged as determined by these actions and their parameters. @@ -5336,24 +5355,24 @@ Requests First, the server headers are read and processed to determine, among other things, the MIME type (document type) and encoding. The headers are then filtered as deterimed by the - +prevent-setting-cookies, - +session-cookies-only, - and +downgrade-http-version + +prevent-setting-cookies, + +session-cookies-only, + and +downgrade-http-version actions. - If the +kill-popups + If the +kill-popups action applies, and it is an HTML or JavaScript document, the popup-code in the response is filtered on-the-fly as it is received. - If a +filter + If a +filter or +deanimate-gifs + url="actions-file.html#DEANIMATE-GIFS">+deanimate-gifs action applies (and the document type fits the action), the rest of the page is read into memory (up to a configurable limit). Then the filter rules (from default.filter) are processed against the buffered @@ -5364,9 +5383,9 @@ Requests Privoxy back to your browser. - If neither +filter + If neither +filter or +deanimate-gifs + url="actions-file.html#DEANIMATE-GIFS">+deanimate-gifs matches, then Privoxy passes the raw data through to the client browser as it becomes available. @@ -5394,8 +5413,8 @@ Requests The way Privoxy applies - actions - and filters + actions + and filters to any given URL can be complex, and not always so easy to understand what is happening. And sometimes we need to be able to see just what Privoxy is @@ -5425,7 +5444,7 @@ Requests Privoxy will tell us how the current configuration will handle it. This will not help with filtering effects (i.e. the +filter action) from + url="actions-file.html#FILTER">+filter action) from the default.filter file since this is handled very differently and not so easy to trap! It also will not tell you about any other URLs that may be embedded within the URL you are testing. For instance, images @@ -5474,7 +5493,7 @@ Requests This tells us how we have defined our - actions, and + actions, and which ones match for our example, google.com. The first listing is any matches for the standard.action file. No hits at all here on standard. Then next is default, or @@ -5492,11 +5511,11 @@ Requests 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 + url="actions-file.html#SESSION-COOKIES-ONLY">+session-cookies-only (i.e. not persistent). So we will allow persistent cookies for google. The second turns off any +fast-redirects + url="actions-file.html#FAST-REDIRECTS">+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 @@ -5560,7 +5579,7 @@ Requests matched three different times. Each as an +block +handle-as-image, which is the expanded form of one of our aliases that had been defined as: +imageblock. (Aliases are defined in + url="actions-file.html#ALIASES">Aliases are defined in the first section of the actions file and typically used to combine more than one action.) @@ -5572,10 +5591,10 @@ Requests though ;-) Note that if you want an ad or obnoxious URL to be invisible, it should be defined as ad.doubleclick.net is done here -- as both a +block + url="actions-file.html#BLOCK">+block and an +handle-as-image. + url="actions-file.html#HANDLE-AS-IMAGE">+handle-as-image. The custom alias +imageblock just simplifies the process and make it more readable. @@ -5711,6 +5730,10 @@ Requests Temple Place - Suite 330, Boston, MA 02111-1307, USA. $Log: user-manual.sgml,v $ + Revision 1.97 2002/04/27 21:04:42 hal9 + -Rewrite of Actions File example. + -Add section for user-manual directive in config. + Revision 1.96 2002/04/27 05:32:00 hal9 -Add short section to Filter Files to tie in with +filter action. -Start rewrite of examples in Actions Examples (not finished). -- 2.39.2