X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fsource%2Fuser-manual.sgml;h=e2a2a7d1515734ef349e870656c317eceaf44e53;hp=3ca6386286661be4de6f0aeef0d1bbea9f3151a2;hb=9e40214d04af75ee0765d4c77145c222d67c3849;hpb=97c15a26185bd3c99025010fd123849545f48cc1
diff --git a/doc/source/user-manual.sgml b/doc/source/user-manual.sgml
index 3ca63862..e2a2a7d1 100644
--- a/doc/source/user-manual.sgml
+++ b/doc/source/user-manual.sgml
@@ -9,8 +9,10 @@
+
+
@@ -18,6 +20,8 @@
+
+
]>
+
+ Copyright &my-copy; 2001, 2002 by
+ Privoxy Developers
+
+
+$Id: user-manual.sgml,v 1.116 2002/05/17 03:23:46 hal9 Exp $
-
+
+
@@ -98,7 +98,7 @@ Hal.
The user manual gives users information on how to install, configure and use
Privoxy.
-
+
&p-intro;
@@ -109,7 +109,7 @@ Hal.
url="http://www.privoxy.org/user-manual/">http://www.privoxy.org/user-manual/.
Please see the Contact section on how to
contact the developers.
-
+
@@ -173,12 +173,11 @@ Hal.
Note: If you have a previous Junkbuster or
Privoxy installation on your system, you
- will need to remove it. Some platforms do this for you as part
- of their installation procedure. (See below for your platform).
- In any case be sure to backup your old configuration
- if it is valuable to you. See the
- note to upgraders section
- below.
+ will need to remove it. On some platforms, this may be done for you as part
+ of their installation procedure. (See below for your platform). In any case
+ be sure to backup your old configuration if it is valuable to
+ you. See the note to
+ upgraders section below.
@@ -188,7 +187,7 @@ How to install the binary packages depends on your operating system:
-Red Hat and SuSE RPMs
+Red Hat, SuSE RPMs and Conectiva
RPMs can be installed with rpm -Uvh privoxy-&p-version;-1.rpm,
@@ -326,8 +325,6 @@ automatically start Privoxy in the boot process.
&buildsource;
-
-
@@ -347,13 +344,13 @@ automatically start Privoxy in the boot process.
and Privoxy configurations will need to be
ported. The functionalities of the old blockfile,
cookiefile and imagelist
- are now combined into the actions
- files
.
+ are now combined into the actions
+ files
.
default.action, is the main actions file. Local
exceptions should best be put into user.action.
- A filter file
(typically
+ 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.
@@ -397,10 +394,10 @@ automatically start Privoxy in the boot process.
- The primary configuration file for cookie management, ad and banner
+ The primary configuration files 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
+ configuration are 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.
@@ -425,61 +422,87 @@ automatically start Privoxy in the boot process.
- If upgrading, please back up any configuration files. See
- the Note to Upgraders Section.
-
+ If upgrading, from versions before 2.9.16, please back up any configuration
+ files. See the Note to Upgraders Section.
+
+
Install Privoxy. See the Installation Section for platform specific
+ linkend="installation">Installation Section below for platform specific
information.
- Start Privoxy, if the installation program has
- not done this already. See the section Starting
- Privoxy.
+ Advanced users and those who want to offer Privoxy
+ service to more than just their local machine should check the main config file, especially the security-relevant options. These are
+ off by default.
- Set your browser to use Privoxy as HTTP and HTTPS
- proxy by setting the proxy configuration for address of
- localhost and port 8118.
- (Junkbuster and earlier versions of
- Privoxy used port 8000.) See the section Starting Privoxy.
+ Start Privoxy, if the installation program has
+ not done this already (may vary according to platform). See the section
+ Starting Privoxy.
+
+
+
+
+
+ Set your browser to use Privoxy as HTTP and
+ HTTPS proxy by setting the proxy configuration for address of
+ 127.0.0.1 and port 8118.
+ (Junkbuster and earlier versions of
+ Privoxy used port 8000.) See the section Starting Privoxy below
+ for more details on this.
- Flush your browser's caches, to remove any cached ad images.
+ Flush your browser's disk and memory caches, to remove any cached ad images.
-
+
- Enjoy surfing with enhanced comfort and privacy. You may want to customize the
- user.action file to
- personalize your new browsing experience. See the Configuration section for more configuration
- options, and how to further customize your installation.
+ A default installation should provide a reasonable starting point for
+ most. There will undoubtedly be occasions where you will want to adjust the
+ configuration, but that can be dealt with as the need arises. Little
+ to no initial configuration is required in most cases.
+
+
+ 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.]]>
-
+
- If you experience problems with sites that misbehave
, see
- the Anatomy of an Action section in the
- Appendix.
+ If you experience ads that slipped through, innocent images that are
+ blocked, or otherwise feel the need to fine-tune
+ Privoxy's behaviour, 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
+ misbehave
.
-
+
Please see the section Contacting the
@@ -488,11 +511,153 @@ automatically start Privoxy in the boot process.
+
+
+ Now enjoy surfing with enhanced comfort and privacy!
+
+
+
+
+
+Quickstart to Ad Blocking
+
+
+ Ad blocking is but one of Privoxy's
+ array of features. Many of these features are for the technically minded advanced
+ user. But, ad blocking is surely common ground for everybody.
+
+
+ This section will provide a quick overview of ad blocking so
+ you can get up to speed quickly without having to read the more extensive
+ information provided below, though this is highly recommeneded.
+
+
+ First a bit of a warning ... blocking ads is much like blocking SPAM: the
+ more aggressive you are about it, the more likely you are to block a few
+ things that were not intended. So there is a trade off here. If you want
+ extreme ad free browsing, be prepared to deal with more
+ problem
sites, and to spend more time adjusting the
+ configuration to solve these unintended consequences.
+
+
+ Secondly, a quick note on Privoxy's
+ actions
. Actions
in this context, are
+ the directives we use to tell Privoxy to perform
+ some task relating to HTTP transactions (i.e. web browsing). We tell
+ Privoxy to take some action
. Each
+ action has a unique name and function. While there are many potential
+ actions in Privoxy's
+ arsenal, only a few are used for ad blocking. Actions, and action
+ configuration files, are explained in depth below.
+
+
+ Actions are specified in Privoxy's configuration,
+ followed by one or more URLs to which the action should apply. URLs
+ can actually be URL type patterns that use
+ wildcards so they can apply potentially to a range of similar URLs.
+
+
+ When you connect to a website, the full path of the URL will either match one
+ of actions as defined in Privoxy's configuration,
+ or not. If so, then Privoxy will perform the
+ action accordingly. If not, then nothing special happens. Futhermore, web
+ pages may contain embedded, secondary URLs that your web browser will
+ display as it parses the original page's HTML content. An ad image for
+ instance, is just a URL embedded in the page somewhere. The image itself may
+ be on the same server, or a server somewhere else on the Internet. Complex
+ web pages will have many such embedded URLs.
+
+
+
+ The actions we need to know about for ad blocking are: block, handle-as-image, and set-image-blocker.
+
+
+
+
+
+
+
+ block - this action stops
+ any contact between your browser and any URL patterns that match this
+ action's configuration. It can be used for blocking ads, but also anything
+ that is determined to be unwanted. By itself, it simply stops any
+ communication with the remote server. If this is the only action that
+ matches for a particular URL, then Privoxy will
+ display its own BLOCKED page to let you now what has happened.
+
+
+
+
+
+ handle-as-image -
+ forces Privoxy to treat this URL as if it were
+ an image. Privoxy knows about common image
+ types (e.g. GIF), but there are many situations where this does not apply.
+ So we'll force it. This is particularly important for ad blocking, since
+ once we can treat it as an image, we can make more intelligent decisisions
+ on how to handle it. There are some limitations to this though. For
+ instance, you can't just force an image substituion for an entire HTML page
+ in most situations.
+
+
+
+
+
+ set-image-blocker -
+ tells Privoxy what to display in place of
+ an ad image that has hit a block rule. For this to come into play,
+ the URL must match a block action somewhere in the configuration.
+ And, it must also either be of a known image type, or
+ match an handle-as-image
+ action.
+
+
+ The configuration options on what to display instead of the ad are:
+
+
+
+ pattern - a checkboard pattern, so that an ad
+ replacement is obvious. This is the default.
+
+
+
+
+ blank - A very small empty GIF image is displayed.
+ This is the so-called invisible
configuration option.
+
+
+
+
+ http://<URL> - A redirect to any URL of the
+ user's choosing.
+
+
+
+
+
+
+
+
+]]>
+
+
+
+
Starting Privoxy
@@ -500,8 +665,8 @@ automatically start Privoxy in the boot process.
Before launching Privoxy for the first time, you
will want to configure your browser(s) to use
Privoxy as a HTTP and HTTPS proxy. The default is
- localhost for the proxy address, and port 8118 (earlier versions used port
- 8000). This is the one configuration step that must be done!
+ 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!
@@ -511,7 +676,7 @@ automatically start Privoxy in the boot process.
For Internet Explorer: Tools ->
Internet Properties -> Connections -> LAN Setting. Then,
check Use Proxy
and fill in the appropriate info (Address:
- localhost, Port: 8118). Include if HTTPS proxy support too.
+ 127.0.0.1, Port: 8118). Include if HTTPS proxy support too.
@@ -530,7 +695,7 @@ automatically start Privoxy in the boot process.
-RedHat and Debian
+RedHat, Conectiva and Debian
We use a script. Note that RedHat does not start Privoxy upon booting per
default. It will use the file /etc/privoxy/config as its
@@ -904,7 +1069,7 @@ must find a better place for this paragraph
Multiple actions files may be defined in config. These
are processed in the order they are defined. Local customizations and locally
preferred exceptions to the default policies as defined in
- default.action (which you will most propably want
+ default.action (which you will most probably want
to define sooner or later) are probably best applied in
user.action, where you can preserve them across
upgrades. standard.action is for
@@ -1142,7 +1307,7 @@ actionsfile
- Default value:
+ Default values:
@@ -1195,7 +1360,7 @@ actionsfile
Specifies:
- The filter file to use
+ The filter file to use
@@ -1216,7 +1381,7 @@ actionsfile
No textual content filtering takes place, i.e. all
- +filter{name}
+ +filter{name}
actions in the actions files are turned neutral.
@@ -1225,13 +1390,25 @@ actionsfile
Notes:
- The default.filter
file contains content modification rules
- that use regular expressions
. These rules permit powerful
- changes on the content of Web pages, e.g., you could disable your favorite
+ The filter file contains content modification
+ rules that use regular expressions. These rules permit
+ powerful changes on the content of Web pages, e.g., you could disable your favorite
JavaScript annoyances, re-write the actual displayed text, or just have some
fun replacing Microsoft
with MicroSuck
wherever
it appears on a Web page.
+
+ The
+ +filter{name}
+ actions rely on the relevant filter (name)
+ to be defined in the filter file!
+
+
+ A pre-defined filter file called default.filter that contains
+ a bunch of handy filters for common problems is included in the distribution.
+ See the section on the filter
+ action for a list.
+
@@ -1410,8 +1587,8 @@ actionsfile
If you intend to operate Privoxy for more users
- that just yourself, it might be a good idea to let them know how to reach
- you, what you block and why you do that, your policies etc.
+ than just yourself, it might be a good idea to let them know how to reach
+ you, what you block and why you do that, your policies, etc.
user-manual
@@ -1450,7 +1627,7 @@ actionsfile
The User Manual URI is used for help links from some of the internal CGI pages.
- The manual itself is normally packaged with the binary distributions, so you propably want
+ The manual itself is normally packaged with the binary distributions, so you probably want
to set this to a locally installed copy. For multi-user setups, you could provide a copy on
a local webserver for all your users and use the corresponding URL here.
@@ -1516,7 +1693,7 @@ actionsfile
The value of this option only matters if the experimental trust mechanism has been
- activated. (See trustfile above.)
+ activated. (See trustfile above.)
If you use the trust mechanism, it is a good idea to write up some on-line
@@ -1646,7 +1823,8 @@ actionsfile
Specifies:
- Key values that determine what information gets logged.
+ Key values that determine what information gets logged to the
+ logfile.
@@ -1796,14 +1974,14 @@ actionsfile
Default value:
- localhost:8118
+ 127.0.0.1:8118
Effect if unset:
- Bind to localhost (127.0.0.1), port 8118. This is suitable and recommended for
+ Bind to 127.0.0.1 (localhost), port 8118. This is suitable and recommended for
home users who run Privoxy on the same machine as
their browser.
@@ -1884,10 +2062,11 @@ actionsfile
If set to 0, Privoxy will start in
toggled off
mode, i.e. behave like a normal, content-neutral
- proxy. See enable-remote-toggle
- below. This is not really useful anymore, since toggling is much easier
- via the web
- interface than via editing the conf file.
+ proxy where all ad blocking, filtering, etc are disabled. See
+ enable-remote-toggle below. This is not really useful
+ anymore, since toggling is much easier via the web interface than via
+ editing the conf file.
The windows version will only display the toggle icon in the system tray
@@ -2059,8 +2238,10 @@ ACLs: permit-access and deny-access
Access controls are included at the request of ISPs and systems
administrators, and are not usually needed by individual users.
For a typical home user, it will normally suffice to ensure that
- Privoxy only listens on the localhost or internal (home)
- network address by means of the listen-address option.
+ Privoxy only listens on the localhost
+ (127.0.0.1) or internal (home) network address by means of the
+ listen-address
+ option.
Please see the warnings in the FAQ that this proxy is not intended to be a substitute
@@ -2670,16 +2851,6 @@ forward-socks4 and forward-socks4a
-
-
- standard.action - is used by the web based editor,
- to set various pre-defined sets of rules for the default actions section
- in default.action. These have increasing levels of
- aggressiveness and have no influence on your browsing unless
- you select them explicitly in the editor. It is not recommend
- to edit this file.
-
-
default.action - is the primary action file
@@ -2699,6 +2870,16 @@ forward-socks4 and forward-socks4a
thing should go here. This file will not be upgraded.
+
+
+ standard.action - is used by the web based editor,
+ to set various pre-defined sets of rules for the default actions section
+ in default.action. These have increasing levels of
+ aggressiveness and have no influence on your browsing unless
+ you select them explicitly in the editor. It is not recommend
+ to edit this file.
+
+
@@ -2777,7 +2958,7 @@ forward-socks4 and forward-socks4a
-
+
How Actions are Applied to URLs
Actions files are divided into sections. There are special sections,
@@ -2812,7 +2993,7 @@ forward-socks4 and forward-socks4a
-
+
Patterns
Generally, a pattern has the form <domain>/<path>,
@@ -3128,46 +3309,44 @@ forward-socks4 and forward-socks4a
+
+
+ Example usage:
+
+
+ +add-header{X-User-Tracking: sucks}
+
+
+
-+block
+block
- Type:
-
+ Typical use:
- Boolean.
+ Block ads or other obnoxious content
- Purpose and typical uses:
+ 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.
- It is typically used to block ads or other obnoxious content.
+ as determined by the handle-as-image
+ and set-image-blocker actions.
- Possible values:
+ Type:
+
- N/A
+ Boolean.
-
+
- Example usage:
+ Parameter:
-
- {+block}
- .banners.example.com
- .ads.r.us
-
+ N/A
-
+
Notes:
- If a URL matches one of the blocked patterns, Privoxy
- will intercept the URL and display its special BLOCKED
page
- instead. If there is sufficient space, a large red banner will appear with
- a friendly message about why the page was blocked, and a way to go there
- anyway. If there is insufficient space a smaller BLOCKED
- page will appear without the red banner.
- Click here
- to view the default blocked HTML page (Privoxy must be running
- for this to work as intended!).
+ Privoxy sends a special BLOCKED
page
+ for requests to blocked pages. This page contains links to find out why the request
+ was blocked, and a click-through to the blocked content (the latter only if compiled with the
+ force feature enabled). The BLOCKED
page adapts to the available
+ screen space -- it displays full-blown if space allows, or miniaturized and text-only
+ if loaded into a small frame or window. If you are using Privoxy
+ right now, you can take a look at the
+ BLOCKED
+ page.
-
- A very important exception is if the URL matches both
- +block
and +handle-as-image
,
- then it will be handled by
- +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.
+ A very important exception occurs if both
+ block and handle-as-image,
+ apply to the same request: it will then be replaced by an image. If
+ set-image-blocker
+ (see below) also applies, the type of image will be determined by its parameter,
+ if not, the standard checkerboard pattern is sent.
+
+
+ It is important to understand this process, in order
+ to understand how Privoxy deals with
+ ads and other unwanted content.
- 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
- reasons.
+ The filter
+ action can perform a very similar task, by blocking
+ banner images and other content through rewriting the relevant URLs in the
+ document's HTML source, so they don't get requested in the first place.
+ Note that this is a totally different technique, and it's easy to confuse the two.
+
+ 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
+
+
+
+
+
-
-
-+deanimate-gifs
+
+crunch-incoming-cookies
- Type:
-
+ Typical use:
- Parameterized.
+
+ Prevent the web server from setting any cookies on your system
+
- Typical uses:
+ Effect:
- To stop those annoying, distracting animated GIF images.
+ Deletes any Set-Cookie:
HTTP headers from server replies.
- Possible values:
+ Type:
+
+
+ Boolean.
+
+
+
+
+ Parameter:
- last
or first
+ N/A
- Example usage:
+ Notes:
-
- {+deanimate-gifs{last}}
- .example.com
-
+
+ This action is only concerned with incoming cookies. For
+ outgoing cookies, use
+ crunch-outgoing-cookies.
+ Use both to disable cookies completely.
+
+
+ It makes no sense at all to use this action in conjunction
+ with the session-cookies-only action,
+ since it would prevent the session cookies from being set.
+
- Notes:
+ Example usage:
- De-animate all animated GIF images, i.e. reduce them to their last frame.
- This will also shrink the images considerably (in bytes, not pixels!). If
- the option first
is given, the first frame of the animation
- is used as the replacement. If last
is given, the last
- frame of the animation is used instead, which probably makes more sense for
- most banner animations, but also has the risk of not showing the entire
- last frame (if it is only a delta to an earlier frame).
+ +crunch-incoming-cookies
-
+
-
-+downgrade-http-version
+
+crunch-outgoing-cookies
- Type:
-
+ Typical use:
- Boolean.
+
+ Prevent the web server from reading any cookies from your system
+
- Typical uses:
+ Effect:
- +downgrade-http-version
will downgrade HTTP/1.1 client requests to
- HTTP/1.0 and downgrade the responses as well.
+ Deletes any Cookie:
HTTP headers from client requests.
- Possible values:
+ Type:
+
+
+ Boolean.
+
+
+
+
+ Parameter:
N/A
@@ -3358,23 +3575,27 @@ forward-socks4 and forward-socks4a
- Example usage:
+ Notes:
-
- {+downgrade-http-version}
- .example.com
-
+
+ This action is only concerned with outgoing cookies. For
+ incoming cookies, use
+ crunch-incoming-cookies.
+ Use both to disable cookies completely.
+
+
+ It makes no sense at all to use this action in conjunction
+ with the session-cookies-only action,
+ since it would prevent the session cookies from being read.
+
- Notes:
+ Example usage:
- Use this action for servers that use HTTP/1.1 protocol features that
- Privoxy doesn't handle well yet. HTTP/1.1 is
- only partially implemented. Default is not to downgrade requests. This is
- an infrequently needed action, and is used to help with rare problem sites only.
+ +crunch-outgoing-cookies
@@ -3382,463 +3603,467 @@ forward-socks4 and forward-socks4a
+
-
-+fast-redirects
+
+deanimate-gifs
- Type:
-
+ Typical use:
- Boolean.
+ Stop those annoying, distracting animated GIF images.
- Typical uses:
+ Effect:
- The +fast-redirects
action enables interception of
- redirect
requests from one server to another, which
- are used to track users.Privoxy can cut off
- all but the last valid URL in a redirect request and send a local redirect
- back to your browser without contacting the intermediate site(s).
+ De-animate GIF animations, i.e. reduce them to their first or last image.
- Possible values:
+ Type:
+
+
+ Parameterized.
+
+
+
+
+ Parameter:
- N/A
+ last
or first
- Example usage:
+ Notes:
-
- {+fast-redirects}
- .example.com
-
+
+ This will also shrink the images considerably (in bytes, not pixels!). If
+ the option first
is given, the first frame of the animation
+ is used as the replacement. If last
is given, the last
+ frame of the animation is used instead, which probably makes more sense for
+ most banner animations, but also has the risk of not showing the entire
+ last frame (if it is only a delta to an earlier frame).
+
+
+ You can safely use this action with patterns that will also match non-GIF
+ objects, because no attempt will be made at anything that doesn't look like
+ a GIF.
+
- Notes:
+ Example usage:
-
- Many sites, like yahoo.com, don't just link to other sites. Instead, they
- will link to some script on their own server, giving the destination as a
- parameter, which will then redirect you to the final target. URLs
- resulting from this scheme typically look like:
- http://some.place/some_script?http://some.where-else.
-
-
- Sometimes, there are even multiple consecutive redirects encoded in the
- URL. These redirections via scripts make your web browsing more traceable,
- since the server from which you follow such a link can see where you go
- to. Apart from that, valuable bandwidth and time is wasted, while your
- browser ask the server for one redirect after the other. Plus, it feeds
- the advertisers.
-
-
- This is a normally on
feature, and often requires exceptions
- for sites that are sensitive to defeating this mechanism.
-
+
+ +deanimate-gifs{last}
+
-
-
-
-+filter
+
+downgrade-http-version
- Type:
-
+ Typical use:
- Parameterized.
+ Work around (very rare) problems with HTTP/1.1
- Typical uses:
+ Effect:
- Apply page filtering as defined by named sections of the
- default.filter file to the specified site(s).
- Filtering
can be any modification of the raw
- page content, including re-writing or deletion of content.
+ Downgrades HTTP/1.1 client requests and server replies to HTTP/1.0.
- Possible values:
+ Type:
+
+
+ Boolean.
+
+
+
+
+ Parameter:
- +filter
must include the name of one of the section identifiers
- from default.filter (or whatever
- filterfile is specified in config).
+ N/A
-
- Example usage (from the current default.filter):
+
+ Notes:
-
-
-
- +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{frameset-borders}: Give frames a border and make them resizable
-
-
-
-
-
- +filter{webbugs}: Squish WebBugs (1x1 invisible GIFs used for user tracking)
-
-
-
-
-
- +filter{refresh-tags}: Kill automatic refresh tags (for dial-on-demand setups)
-
-
-
-
-
- +filter{fun}: Text replacements for subversive browsing fun!
-
-
-
-
-
- +filter{nimda}: Remove Nimda (virus) code.
-
-
-
-
-
- +filter{banners-by-size}: Kill banners by size (very efficient!)
-
-
-
-
-
- +filter{shockwave-flash}: Kill embedded Shockwave Flash objects
-
-
-
-
-
- +filter{crude-parental}: Kill all web pages that contain the words "sex" or "warez"
-
-
+
+ This is a left-over from the time when Privoxy
+ didn't support important HTTP/1.1 features well. It is left here for the
+ unlikely case that you experience HTTP/1.1 related problems with some server
+ out there. Not all (optional) HTTP/1.1 features are supported yet, so there
+ is a chance you might need this action.
+
- Notes:
+ Example usage (section):
-
- This is potentially a very powerful feature! And requires a knowledge
- of regular expressions if you want to roll your own
.
- Filtering operates on a line by line basis throughout the entire page.
-
-
- Filtering requires buffering the page content, which may appear to
- slow down page rendering since nothing is displayed until all content has
- passed the filters. (It does not really take longer, but seems that way
- since the page is not incrementally displayed.) This effect will be more
- noticeable on slower connections.
-
-
- Filtering can achieve some of the effects as the
- +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
- already filtered
page.
-
+
+ {+downgrade-http-version}
+problem-host.example.com
+
-
-