| Privoxy User Manual | Privoxy 2.9.16 User Manual|
|---|---|
| Prev | Next | +filter{banners-by-size} # Kill banners based on their size for this page (+filter{banners-by-size} # Kill banners based on their size for this page (very efficient!) |
+filter{banners-by-link} # Kill banners based on the link they are contained in (experimental) |
+filter{img-reorder} # Reorder attributes in <img> tags to make the banners-by-* filters more effective |
+filter{js-events} # Kill all JS event bindings (Radically destructive! Only for extra nasty sites) |
Mark URLs as belonging to images (so they'll be replaced by images Mark URLs as belonging to images (so they'll be replaced by images if they get blocked)
This breaks many web sites that depend on looking at this header in order
to customize their content for different browsers (which, by the
- way, is NOT a Privoxy is
- not recommended. In single-user, single-browser
setups, you might use it to delete your OS version information from
the headers, because it is an invitation to exploit known bugs for your
@@ -2702,9 +2718,11 @@ CLASS="SECT3"
>8.5.14. kill-popups8.5.14. kill-popups
It makes It makes no sense at all to use session-cookies-only
This action alone doesn't do anything noticeable. If This action alone doesn't do anything noticeable. If both block and handle-as-image also apply, i.e. if the request is to be blocked as an image, - then the parameter of this action decides what will be sent as a replacement.
There is a third (advanced) type, called "auto". It is . It is NOT to be used inNote that many of these actions have the potential to cause a page to misbehave, possibly even not to display at all. There are many ways @@ -3653,7 +3661,9 @@ CLASS="SECT2" >
Custom and "}", but we , but we strongly recommend that you only use "a" sign, since they are merely textually expanded.
Aliases can be used throughout the actions file, but they Aliases can be used throughout the actions file, but they must be
defined in a special section at the top of the file!
And there can only be one such section per actions file. Each actions file may
have its own alias section, and the aliases defined in it are only visible
@@ -3734,12 +3738,9 @@ CLASS="EMPHASIS"
CLASS="QUOTE"
>"shop", you can later change your policy on shops in
- one place, and your changes will take effect everywhere
in the actions file where the The above chapters have shown Every config file should start with a short comment stating its purpose: Now come the regular sections, i.e. sets of actions, accompanied
- by URL patterns to which they apply. Remember all actions
are disabled when matching starts, so we have to explicitly
enable the ones we want. "default" And then there are known banner sources. They often use scripts to
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
e.g. catches
"nasty-"nasty-ads.nasty-corp.com" as intended,
but also "downlo"downloads.sourcefroge.net" or
""adsl.some-provider.net." So here come some
well-known exceptions to the -block8.7. Actions Files Tutorial
8.7. Actions Files Tutorial8.7.1. default.action
8.7.1. default.action
| Home | Next |