X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Fappendix.html;h=8b4b69825e89967f5df16437a8ca8c82b46fc83e;hb=016253d925d92fe8770ad306bb84c14ff8b1027e;hp=5206ae5e240917a67842e85de37c42e0701eaa6f;hpb=0a3750f6302df8349b5be2e15a9a4fefe3c35889;p=privoxy.git diff --git a/doc/webserver/user-manual/appendix.html b/doc/webserver/user-manual/appendix.html index 5206ae5e..8b4b6982 100644 --- a/doc/webserver/user-manual/appendix.html +++ b/doc/webserver/user-manual/appendix.html @@ -4,17 +4,19 @@ >Appendix + +
Now another example,
{ +block +handle-as-image } - .ad.doubleclick.net - - { +block +handle-as-image } +> { +block } ad*. + { +block } + .ad. + { +block +handle-as-image } - .doubleclick.net
We'll just show the interesting part here, the explicit matches. It is - matched three different times. Each as an 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""ad.doubleclick.net" is done here -- as both a "+block" - and an "+handle-as-image". The custom alias "+imageblock" just simplifies the process and make - it more readable.
"+block-as-image" just + simplifies the process and make it more readable.One last example. Let's try "http://www.rhapsodyk.net/adsl/HOWTO/""http://www.example.net/adsl/HOWTO/". - This one is giving us problems. We are getting a blank page. Hmmm...
Matches for http://www.rhapsodyk.net/adsl/HOWTO/: +> Matches for http://www.example.net/adsl/HOWTO/: - { -add-header -block +deanimate-gifs -downgrade-http-version +fast-redirects - +filter{html-annoyances} +filter{js-annoyances} +filter{kill-popups} - +filter{webbugs} +filter{nimda} +filter{banners-by-size} +filter{hal} - +filter{fun} +hide-forwarded-for-headers +hide-from-header{block} - +hide-referer{forge} -hide-user-agent -handle-as-image +set-image-blocker{blank} - +prevent-compression +session-cookies-only -prevent-setting-cookies - -prevent-reading-cookies +kill-popups -send-vanilla-wafer -send-wafer } + In file: default.action [ View ] [ Edit ] + + {-add-header + -block + -content-type-overwrite + -crunch-client-header + -crunch-if-none-match + -crunch-incoming-cookies + -crunch-outgoing-cookies + -crunch-server-header + +deanimate-gifs + -downgrade-http-version + +fast-redirects{check-decoded-url} + +filter{html-annoyances} + +filter{js-annoyances} + +filter{kill-popups} + +filter{webbugs} + +filter{nimda} + +filter{banners-by-size} + +filter{hal} + +filter{fun} + -filter-client-headers + -filter-server-headers + -force-text-mode + -handle-as-empty-document + -handle-as-image + -hide-accept-language + -hide-content-disposition + +hide-forwarded-for-headers + +hide-from-header{block} + +hide-referer{forge} + -hide-user-agent + -inspect-jpegs + +kill-popups + -overwrite-last-modified + +prevent-compression + -redirect + -send-vanilla-wafer + -send-wafer + +session-cookies-only + +set-image-blocker{blank} + -treat-forbidden-connects-like-blocks } / { +block +handle-as-image } @@ -1717,20 +1875,38 @@ CLASS="QUOTE" > is matching "/ads"! 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 does in our + configuration! But we did not want this at all! Now we see why we get the + blank page. It is actually triggering two different actions here, and + the effects are aggregated so that the URL is blocked, and Privoxy 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 + not - block (un blocks ( + "{-block}") paths with ) paths with + "adsl". There are - various ways to handle such exceptions. Example: in them (remember, last match in the configuration + wins). There are various ways to handle such exceptions. Example: Now the page displays ;-) Be sure to flush your browser's caches when - making such changes. Or, try using 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. |
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 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. Try - adding the URL for the site to one of aliases that turn off "+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 @@ -1805,14 +1995,20 @@ CLASS="SCREEN" > |
This would probably be most appropriately put in This would turn off all filtering for these sites. This is best + put in user.action, - for local site exceptions.
, 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).
"{ 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 |
Remember to flush caches! Note that the + mail.google reference lacks the TLD portion (e.g. + "{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.
".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.