CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.6 User Manual"
+TITLE="Privoxy 3.0.7 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="The Main Configuration File"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.6 User Manual</TH
+>Privoxy 3.0.7 User Manual</TH
></TR
><TR
><TD
> <DIV
CLASS="TABLE"
><A
-NAME="AEN2003"
+NAME="AEN2061"
></A
><P
><B
<TT
CLASS="FILENAME"
>default.action</TT
-> is typically process before
+> is typically processed before
<TT
CLASS="FILENAME"
>user.action</TT
><H2
CLASS="SECT2"
><A
-NAME="AEN2102"
+NAME="AEN2160"
></A
>8.1. Finding the Right Mix</H2
><P
><H2
CLASS="SECT2"
><A
-NAME="AEN2109"
+NAME="AEN2167"
></A
>8.2. How to Edit</H2
><P
><A
NAME="ACTIONS-APPLY"
></A
->8.3. How Actions are Applied to URLs</H2
+>8.3. How Actions are Applied to Requests</H2
><P
> Actions files are divided into sections. There are special sections,
like the <SPAN
be discussed later. For now let's concentrate on regular sections: They have a
heading line (often split up to multiple lines for readability) which consist
of a list of actions, separated by whitespace and enclosed in curly braces.
- Below that, there is a list of URL patterns, each on a separate line.</P
+ Below that, there is a list of URL and tag patterns, each on a separate line.</P
><P
> To determine which actions apply to a request, the URL of the request is
- compared to all patterns in each <SPAN
+ compared to all URL patterns in each <SPAN
CLASS="QUOTE"
>"action file"</SPAN
-> 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,
- the effects are aggregated. E.g. a URL might match a regular section with
- a heading line of <TT
+>.
+ Every time it matches, the list of applicable actions for the request is
+ incrementally updated, using the heading of the section in which the
+ pattern is located. The same is done again for tags and tag patterns later on.</P
+><P
+> If multiple applying sections set the same action differently,
+ the last match wins. If not, the effects are aggregated.
+ E.g. a URL might match a regular section with a heading line of <TT
CLASS="LITERAL"
>{
+<A
>
</P
><P
-> You can trace this process for any given URL by visiting <A
+> You can trace this process for
URL patterns and any given URL by visiting <A
HREF="http://config.privoxy.org/show-url-info"
TARGET="_top"
>http://config.privoxy.org/show-url-info</A
flexibility. This allows one expression to be expanded and potentially match
against many similar patterns.</P
><P
-> Generally, a <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> pattern has the form
+> Generally, a URL pattern has the form
<TT
CLASS="LITERAL"
><domain>/<path></TT
><H3
CLASS="SECT3"
><A
-NAME="AEN2192"
+NAME="AEN2250"
></A
>8.4.1. The Domain Pattern</H3
><P
><H3
CLASS="SECT3"
><A
-NAME="AEN2263"
+NAME="AEN2321"
></A
>8.4.2. The Path Pattern</H3
><P
>Appendix on regular expressions</A
>.</P
></DIV
+><DIV
+CLASS="SECT3"
+><H3
+CLASS="SECT3"
+><A
+NAME="TAG-PATTERN"
+></A
+>8.4.3. The Tag Pattern</H3
+><P
+> Tag patterns are used to change the applying actions based on the
+ request's tags. Tags can be created with either the
+ <A
+HREF="actions-file.html#CLIENT-HEADER-FILTER"
+>client-header-tagger</A
+>
+ or the <A
+HREF="actions-file.html#SERVER-HEADER-FILTER"
+>server-header-tagger</A
+> action.</P
+><P
+> Tag patterns have to start with <SPAN
+CLASS="QUOTE"
+>"TAG:"</SPAN
+>, so <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+>
+ can tell them apart from URL patterns. Everything after the colon
+ including white space, is interpreted as a regular expression with
+ path patterns syntax, except that tag patterns aren't left-anchored
+ automatically (Privoxy doesn't silently add a <SPAN
+CLASS="QUOTE"
+>"^"</SPAN
+>,
+ you have to do it yourself if you need it).</P
+><P
+> To match all requests that are tagged with <SPAN
+CLASS="QUOTE"
+>"foo"</SPAN
+>
+ your pattern line should be <SPAN
+CLASS="QUOTE"
+>"TAG:^foo$"</SPAN
+>,
+ <SPAN
+CLASS="QUOTE"
+>"TAG:foo"</SPAN
+> would work as well, but it would also
+ match requests whose tags contain <SPAN
+CLASS="QUOTE"
+>"foo"</SPAN
+> somewhere.</P
+><P
+> Sections can contain URL and tag patterns at the same time,
+ but tag patterns are checked after the URL patterns and thus
+ always overrule them, even if they are located before the URL patterns.</P
+><P
+> Once a new tag is added, Privoxy checks right away if it's matched by one
+ of the tag patterns and updates the action settings accordingly. As a result
+ tags can be used to activate other tagger actions, as long as these other
+ taggers look for headers that haven't already be parsed.</P
+><P
+> For example you could tag client requests which use the POST method,
+ use this tag to activate another tagger that adds a tag if cookies
+ are send, and then block based on the cookie tag. However if you'd
+ reverse the position of the described taggers, and activated the method
+ tagger based on the cookie tagger, no method tags would be created.
+ The method tagger would look for the request line, but at the time
+ the cookie tag is created the request line has already been parsed.</P
+><P
+> While this is a limitation you should be aware of, this kind of
+ indirection is seldom needed anyway and even the example doesn't
+ make too much sense.</P
+></DIV
></DIV
><DIV
CLASS="SECT2"
><H4
CLASS="SECT3"
><A
+NAME="CLIENT-HEADER-FILTER"
+></A
+>8.5.3. client-header-filter</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>Typical use:</DT
+><DD
+><P
+> Rewrite or remove single client headers.
+ </P
+></DD
+><DT
+>Effect:</DT
+><DD
+><P
+> All client headers to which this action applies are filtered on-the-fly through
+ the specified regular expression based substitutions.
+ </P
+></DD
+><DT
+>Type:</DT
+><DD
+><P
+>Parameterized.</P
+></DD
+><DT
+>Parameter:</DT
+><DD
+><P
+> The name of a client-header filter, as defined in one of the
+ <A
+HREF="filter-file.html"
+>filter files</A
+>.
+ </P
+></DD
+><DT
+>Notes:</DT
+><DD
+><P
+> Client-header filters are applied to each header on its own, not to
+ all at once. This makes it easier to diagnose problems, but on the downside
+ you can't write filters that only change header x if header y's value is z.
+ You can do that by using tags though.
+ </P
+><P
+> Client-header filters are executed after the other header actions have finished
+ and use their output as input.
+ </P
+><P
+> Please refer to the <A
+HREF="filter-file.html"
+>filter file chapter</A
+>
+ to learn which client-header filters are available by default, and how to
+ create your own.
+ </P
+></DD
+><DT
+>Example usage (section):</DT
+><DD
+><P
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="90%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+>{+client-header-filter{hide-tor-exit-notation}}
+.exit/
+ </PRE
+></TD
+></TR
+></TABLE
+>
+ </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><H4
+CLASS="SECT3"
+><A
+NAME="CLIENT-HEADER-TAGGER"
+></A
+>8.5.4. client-header-tagger</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>Typical use:</DT
+><DD
+><P
+> Block requests based on their headers.
+ </P
+></DD
+><DT
+>Effect:</DT
+><DD
+><P
+> Client headers to which this action applies are filtered on-the-fly through
+ the specified regular expression based substitutions, the result is used as
+ tag.
+ </P
+></DD
+><DT
+>Type:</DT
+><DD
+><P
+>Parameterized.</P
+></DD
+><DT
+>Parameter:</DT
+><DD
+><P
+> The name of a client-header tagger, as defined in one of the
+ <A
+HREF="filter-file.html"
+>filter files</A
+>.
+ </P
+></DD
+><DT
+>Notes:</DT
+><DD
+><P
+> Client-header taggers are applied to each header on its own,
+ and as the header isn't modified, each tagger <SPAN
+CLASS="QUOTE"
+>"sees"</SPAN
+>
+ the original.
+ </P
+><P
+> Client-header taggers are the first actions that are executed
+ and their tags can be used to control every other action.
+ </P
+></DD
+><DT
+>Example usage (section):</DT
+><DD
+><P
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="90%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+># Tag every request with the User-Agent header
+{+client-header-filter{user-agent}}
+/
+ </PRE
+></TD
+></TR
+></TABLE
+>
+ </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><H4
+CLASS="SECT3"
+><A
NAME="CONTENT-TYPE-OVERWRITE"
></A
->8.5.3. content-type-overwrite</H4
+>8.5.5. content-type-overwrite</H4
><P
></P
><DIV
This limitation exists for a reason, think twice before circumventing it.
</P
><P
-> Most of the time it's easier to enable
+> Most of the time it's easier to replace this action with a custom
<TT
CLASS="LITERAL"
><A
-HREF="actions-file.html#FILTER-SERVER-HEADERS"
->filter-server-headers</A
+HREF="actions-file.html#SERVER-HEADER-FILTER"
+>server-header filter</A
></TT
->
- and replace this action with a custom regular expression. It allows you
- to activate it for every document of a certain site and it will still
+>.
+ It allows you to activate it for every document of a certain site and it will still
only replace the content types you aimed at.
</P
><P
# but leave the content type unmodified if the URL looks like a style sheet
{-content-type-overwrite}
-www.example.net/*.\.css$
-www.example.net/*.style</PRE
+www.example.net/.*\.css$
+www.example.net/.*style</PRE
></TD
></TR
></TABLE
><A
NAME="CRUNCH-CLIENT-HEADER"
></A
->8.5.4. crunch-client-header</H4
+>8.5.6. crunch-client-header</H4
><P
></P
><DIV
>crunch-client-header</TT
> is only meant for quick tests.
If you have to block several different headers, or only want to modify
- parts of them, you should enable
+ parts of them, you should use a
<TT
CLASS="LITERAL"
><A
-HREF="actions-file.html#FILTER-CLIENT-HEADERS"
->filter-client-headers</A
+HREF="actions-file.html#CLIENT-HEADER-FILTER"
+>client-header filter</A
></TT
->
- and create your own filter.
+>.
</P
><DIV
CLASS="WARNING"
><A
NAME="CRUNCH-IF-NONE-MATCH"
></A
->8.5.5. crunch-if-none-match</H4
+>8.5.7. crunch-if-none-match</H4
><P
></P
><DIV
><A
NAME="CRUNCH-INCOMING-COOKIES"
></A
->8.5.6. crunch-incoming-cookies</H4
+>8.5.8. crunch-incoming-cookies</H4
><P
></P
><DIV
><A
NAME="CRUNCH-SERVER-HEADER"
></A
->8.5.7. crunch-server-header</H4
+>8.5.9. crunch-server-header</H4
><P
></P
><DIV
>crunch-server-header</TT
> is only meant for quick tests.
If you have to block several different headers, or only want to modify
- parts of them, you should enable
+ parts of them, you should use a custom
<TT
CLASS="LITERAL"
><A
-HREF="actions-file.html#FILTER-SERVER-HEADERS"
->filter-server-headers</A
+HREF="actions-file.html#SERVER-HEADER-FILTER"
+>server-header filter</A
></TT
->
- and create your own filter.
+>.
</P
><DIV
CLASS="WARNING"
><A
NAME="CRUNCH-OUTGOING-COOKIES"
></A
->8.5.8. crunch-outgoing-cookies</H4
+>8.5.10. crunch-outgoing-cookies</H4
><P
></P
><DIV
><A
NAME="DEANIMATE-GIFS"
></A
->8.5.9. deanimate-gifs</H4
+>8.5.11. deanimate-gifs</H4
><P
></P
><DIV
><A
NAME="DOWNGRADE-HTTP-VERSION"
></A
->8.5.10. downgrade-http-version</H4
+>8.5.12. downgrade-http-version</H4
><P
></P
><DIV
><A
NAME="FAST-REDIRECTS"
></A
->8.5.11. fast-redirects</H4
+>8.5.13. fast-redirects</H4
><P
></P
><DIV
or lead to a <SPAN
CLASS="QUOTE"
>"page not found"</SPAN
-> error. It is possible to fix these redirected
- requests with <TT
+> error. You can prevent this problem by
+ first using the <TT
CLASS="LITERAL"
><A
-HREF="actions-file.html#FILTER-CLIENT-HEADERS"
->filter-client-headers</A
+HREF="actions-file.html#REDIRECT"
+>redirect</A
></TT
->
- but it requires a little effort.
+> action
+ to remove the last part of the URL, but it requires a little effort.
</P
><P
> To detect a redirection URL, <TT
><A
NAME="FILTER"
></A
->8.5.12. filter</H4
+>8.5.14. filter</H4
><P
></P
><DIV
>Effect:</DT
><DD
><P
-> All files of text-based type, most notably HTML and
- JavaScript, to which this action applies, can be 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 <TT
+> All instances of text-based type, most notably HTML and JavaScript, to which
+ this action applies, can be 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
+ <TT
CLASS="LITERAL"
>text/plain</TT
-> MIME type for all
- files whose type they don't know.) By default, filtering works only on the
- raw document content itself (that which can be seen with <TT
-CLASS="LITERAL"
->View
- Source</TT
->),
- not the headers.
+> MIME type for all files whose type they don't know.)
</P
></DD
><DT
>Parameter:</DT
><DD
><P
-> The name of a filter, as defined in the <A
+> The name of a
content filter, as defined in the <A
HREF="filter-file.html"
>filter file</A
>.
> exceptions.
</P
><P
-> At this time, <SPAN
+> Compressed content can't be filtered either, unless <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> cannot uncompress compressed
- documents. If you want filtering to work on all documents, even those that
- would normally be sent compressed, you must use the
- <TT
+>
+ is compiled with zlib support (requires at least <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> 3.0.7),
+ in which case <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> will decompress the content before filtering
+ it.
+ </P
+><P
+> If you use a <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> version without zlib support, but want filtering to work on
+ as much documents as possible, even those that would normally be sent compressed,
+ you must use the <TT
CLASS="LITERAL"
><A
HREF="actions-file.html#PREVENT-COMPRESSION"
>.
</P
><P
-> Filtering can achieve some of the same effects as the
+> Content filtering can achieve some of the same effects as the
<TT
CLASS="LITERAL"
><A
</P
><P
> <A
-NAME="FILTER-HTML-TO-XML"
-></A
->
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="90%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
->+filter{html-to-xml} # Header filter to change the Content-Type from html to xml</PRE
-></TD
-></TR
-></TABLE
->
- </P
-><P
-> <A
-NAME="FILTER-XML-TO-HTML"
-></A
->
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="90%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
->+filter{xml-to-html} # Header filter to change the Content-Type from xml to html</PRE
-></TD
-></TR
-></TABLE
->
- </P
-><P
-> <A
NAME="FILTER-NO-PING"
></A
>
></TD
></TR
></TABLE
->
- </P
-><P
-> <A
-NAME="FILTER-HIDE-TOR-EXIT-NOTATION"
-></A
->
- <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="90%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
->+filter{hide-tor-exit-notation} # Header filter to remove the Tor exit node notation in Host and Referer headers</PRE
-></TD
-></TR
-></TABLE
>
</P
></DD
><H4
CLASS="SECT3"
><A
-NAME="FILTER-CLIENT-HEADERS"
+NAME="FORCE-TEXT-MODE"
></A
->8.5.13. filter-client-headers</H4
+>8.5.15. force-text-mode</H4
><P
></P
><DIV
>Typical use:</DT
><DD
><P
-> To apply filtering to the client's (browser's) headers
- </P
+>Force <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> to treat a document as if it was in some kind of <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>text</I
+></SPAN
+> format. </P
></DD
><DT
>Effect:</DT
><DD
><P
-> By default, <SPAN
-CLASS="APPLICATION"
->Privoxy's</SPAN
-> filters only apply
- to the document content itself. This will extend those filters to
- include the client's headers as well.
+> Declares a document as text, even if the <SPAN
+CLASS="QUOTE"
+>"Content-Type:"</SPAN
+> isn't detected as such.
</P
></DD
><DT
>Notes:</DT
><DD
><P
-> Regular expressions can be used to filter headers as well. Check your
- filters closely before activating this action, as it can easily lead to broken
- requests.
- </P
-><P
->
- These filters are applied to each header on its own, not to them
- all at once. This makes it easier to diagnose problems, but on the downside
- you can't write filters that only change header x if header y's value is
- z.
- </P
-><P
-> The filters are used after the other header actions have finished and can
- use their output as input.
- </P
-><P
-> Whenever possible one should specify <TT
+> As explained <TT
CLASS="LITERAL"
->^</TT
+><A
+HREF="actions-file.html#FILTER"
+>above</A
+></TT
>,
- <TT
-CLASS="LITERAL"
->$</TT
->, the whole header name and the colon, to make sure
- the filter doesn't cause havoc to other headers or the
- page itself. For example if you want to transform
<SPAN
CLASS="APPLICATION"
->Galeon</SPAN
-> User-Agents to
- <SPAN
-CLASS="APPLICATION"
->Firefox</SPAN
-> User-Agents you
- shouldn't use:</P
+>Privoxy</SPAN
+> tries to only filter files that are
+ in some kind of text format. The same restrictions apply to
+ <TT
+CLASS="LITERAL"
+><A
+HREF="actions-file.html#CONTENT-TYPE-OVERWRITE"
+>content-type-overwrite</A
+></TT
+>.
+ <TT
+CLASS="LITERAL"
+>force-text-mode</TT
+> declares a document as text,
+ without looking at the <SPAN
+CLASS="QUOTE"
+>"Content-Type:"</SPAN
+> first.
+ </P
+><DIV
+CLASS="WARNING"
><P
+></P
><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
+CLASS="WARNING"
+BORDER="1"
WIDTH="90%"
><TR
><TD
-><PRE
-CLASS="SCREEN"
->s@Galeon/\d\.\d\.\d @@</PRE
+ALIGN="CENTER"
+><B
+>Warning</B
></TD
></TR
-></TABLE
-></P
-><P
-> but:</P
-><P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="90%"
><TR
><TD
-><PRE
-CLASS="SCREEN"
->s@^(User-Agent:.*) Galeon/\d\.\d\.\d (Firefox/\d\.\d\.\d\.\d)$@$1 $2@</PRE
+ALIGN="LEFT"
+><P
+> Think twice before activating this action. Filtering binary data
+ with regular expressions can cause file damage.
+ </P
></TD
></TR
></TABLE
-></P
+></DIV
></DD
><DT
->Example usage (section):</DT
+>Example usage:</DT
><DD
><P
> <TABLE
><TD
><PRE
CLASS="SCREEN"
->{+filter-client-headers +filter{test_filter}}
-problem-host.example.com
- </PRE
+>+force-text-mode
+ </PRE
></TD
></TR
></TABLE
>
- </P
+ </P
></DD
></DL
></DIV
><H4
CLASS="SECT3"
><A
-NAME="FILTER-SERVER-HEADERS"
+NAME="FORWARD-OVERRIDE"
></A
->8.5.14. filter-server-headers</H4
+>8.5.16. forward-override</H4
><P
></P
><DIV
>Typical use:</DT
><DD
><P
-> To apply filtering to the server's headers
- </P
+>Change the forwarding settings based on User-Agent or request origin</P
></DD
><DT
>Effect:</DT
><DD
><P
-> By default, <SPAN
-CLASS="APPLICATION"
->Privoxy's</SPAN
-> filters only apply
- to the document content itself. This will extend those filters to
- include the server's headers as well.
+> Overrules the forward directives in the configuration files.
</P
></DD
><DT
>Type:</DT
><DD
><P
->Boolean.</P
+>Multi-value.</P
></DD
><DT
>Parameter:</DT
><DD
><P
-> N/A
- </P
-></DD
-><DT
->Notes:</DT
-><DD
-><P
-> Similar to <TT
-CLASS="LITERAL"
->filter-client-headers</TT
->, but works on
- the server instead. To filter both server and client, use both.
- </P
-><P
-> As with <TT
-CLASS="LITERAL"
->filter-client-headers</TT
->, check your
- filters before activating this action, as it can easily lead to broken
- requests.
- </P
-><P
->
- These filters are applied to each header on its own, not to them
- all at once. This makes it easier to diagnose problems, but on the downside
- you can't write filters that only change header x if header y's value is
- z.
- </P
-><P
-> The filters are used after the other header actions have finished and can
- use their output as input.
- </P
-><P
-> Remember too, whenever possible one should specify <TT
-CLASS="LITERAL"
->^</TT
->,
- <TT
-CLASS="LITERAL"
->$</TT
->, the whole header name and the colon, to make sure
- the filter doesn't cause havoc to other headers or the
- page itself. See above for example.
- </P
-></DD
-><DT
->Example usage (section):</DT
-><DD
-><P
-> <TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="90%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
->{+filter-server-headers +filter{test_filter}}
-problem-host.example.com
- </PRE
-></TD
-></TR
-></TABLE
->
- </P
-></DD
-></DL
-></DIV
-></DIV
-><DIV
-CLASS="SECT3"
-><H4
-CLASS="SECT3"
-><A
-NAME="FORCE-TEXT-MODE"
-></A
->8.5.15. force-text-mode</H4
-><P
></P
-><DIV
-CLASS="VARIABLELIST"
-><DL
-><DT
->Typical use:</DT
-><DD
+><UL
+><LI
><P
->Force <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> to treat a document as if it was in some kind of <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->text</I
-></SPAN
-> format. </P
-></DD
-><DT
->Effect:</DT
-><DD
+><SPAN
+CLASS="QUOTE"
+>"forward ."</SPAN
+> to use a direct connection without any additional proxies.</P
+></LI
+><LI
><P
-> Declares a document as text, even if the <SPAN
+> <SPAN
CLASS="QUOTE"
->"Content-Type:"</SPAN
-> isn't detected as such.
- </P
-></DD
-><DT
->Type:</DT
-><DD
+>"forward 127.0.0.1:8123"</SPAN
+> to use the HTTP proxy listening at 127.0.0.1 port 8123.
+ </P
+></LI
+><LI
><P
->Boolean.</P
-></DD
-><DT
->Parameter:</DT
-><DD
+> <SPAN
+CLASS="QUOTE"
+>"forward-socks4a 127.0.0.1:9050 ."</SPAN
+> to use the socks4a proxy listening at 127.0.0.1 port 9050.
+ Replace <SPAN
+CLASS="QUOTE"
+>"forward-socks4a"</SPAN
+> with <SPAN
+CLASS="QUOTE"
+>"forward-socks4"</SPAN
+> to use a socks4 connection (with local DNS
+ resolution) instead.
+ </P
+></LI
+><LI
><P
-> N/A
- </P
+> <SPAN
+CLASS="QUOTE"
+>"forward-socks4a 127.0.0.1:9050 proxy.example.org:8000"</SPAN
+> to use the socks4a proxy
+ listening at 127.0.0.1 port 9050 to reach the HTTP proxy listening at proxy.example.org port 8000.
+ Replace <SPAN
+CLASS="QUOTE"
+>"forward-socks4a"</SPAN
+> with <SPAN
+CLASS="QUOTE"
+>"forward-socks4"</SPAN
+> to use a socks4 connection (with local DNS
+ resolution) instead.
+ </P
+></LI
+></UL
></DD
><DT
>Notes:</DT
><DD
><P
-> As explained <TT
-CLASS="LITERAL"
-><A
-HREF="actions-file.html#FILTER"
->above</A
-></TT
->,
- <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> tries to only filter files that are
- in some kind of text format. The same restrictions apply to
- <TT
-CLASS="LITERAL"
-><A
-HREF="actions-file.html#CONTENT-TYPE-OVERWRITE"
->content-type-overwrite</A
-></TT
->.
- <TT
-CLASS="LITERAL"
->force-text-mode</TT
-> declares a document as text,
- without looking at the <SPAN
-CLASS="QUOTE"
->"Content-Type:"</SPAN
-> first.
+> This action takes parameters similar to the
+ <A
+HREF="config.html#FORWARDING"
+>forward</A
+> directives in the configuration
+ file, but without the URL pattern. It can be used as replacement, but normally it's only
+ used in cases where matching based on the request URL isn't sufficient.
</P
><DIV
CLASS="WARNING"
><TD
ALIGN="LEFT"
><P
-> Think twice before activating this action. Filtering binary data
- with regular expressions can cause file damage.
+> Please read the description for the <A
+HREF="config.html#FORWARDING"
+>forward</A
+> directives before
+ using this action. Forwarding to the wrong people will reduce your privacy and increase the
+ chances of man-in-the-middle attacks.
+ </P
+><P
+> If the ports are missing or invalid, default values will be used. This might change
+ in the future and you shouldn't rely on it. Otherwise incorrect syntax causes Privoxy
+ to exit.
+ </P
+><P
+> Use the <A
+HREF="http://config.privoxy.org/show-url-info"
+TARGET="_top"
+>show-url-info CGI page</A
+>
+ to verify that your forward settings do what you thought the do.
</P
></TD
></TR
><TD
><PRE
CLASS="SCREEN"
->+force-text-mode
+># Always use direct connections for requests previously tagged as
+# <SPAN
+CLASS="QUOTE"
+>"User-Agent: fetch libfetch/2.0"</SPAN
+> and make sure
+# resuming downloads continues to work.
+# This way you can continue to use Tor for your normal browsing,
+# without overloading the Tor network with your FreeBSD ports updates
+# or downloads of bigger files like ISOs.
+{+forward-override{forward .} \
+ -hide-if-modified-since \
+ -overwrite-last-modified \
+}
+TAG:^User-Agent: fetch libfetch/2.0$
</PRE
></TD
></TR
><A
NAME="HANDLE-AS-EMPTY-DOCUMENT"
></A
->8.5.16. handle-as-empty-document</H4
+>8.5.17. handle-as-empty-document</H4
><P
></P
><DIV
><A
NAME="HANDLE-AS-IMAGE"
></A
->8.5.17. handle-as-image</H4
+>8.5.18. handle-as-image</H4
><P
></P
><DIV
><A
NAME="HIDE-ACCEPT-LANGUAGE"
></A
->8.5.18. hide-accept-language</H4
+>8.5.19. hide-accept-language</H4
><P
></P
><DIV
><A
NAME="HIDE-CONTENT-DISPOSITION"
></A
->8.5.19. hide-content-disposition</H4
+>8.5.20. hide-content-disposition</H4
><P
></P
><DIV
{ -filter \
+content-type-overwrite{text/plain}\
+hide-content-disposition{block} }
- .sourceforge.net/tracker/download.php</PRE
+ .sourceforge.net/tracker/download\.php</PRE
></TD
></TR
></TABLE
><A
NAME="HIDE-IF-MODIFIED-SINCE"
></A
->8.5.20. hide-if-modified-since</H4
+>8.5.21. hide-if-modified-since</H4
><P
></P
><DIV
><A
NAME="HIDE-FORWARDED-FOR-HEADERS"
></A
->8.5.21. hide-forwarded-for-headers</H4
+>8.5.22. hide-forwarded-for-headers</H4
><P
></P
><DIV
><A
NAME="HIDE-FROM-HEADER"
></A
->8.5.22. hide-from-header</H4
+>8.5.23. hide-from-header</H4
><P
></P
><DIV
><A
NAME="HIDE-REFERRER"
></A
->8.5.23. hide-referrer</H4
+>8.5.24. hide-referrer</H4
><A
NAME="HIDE-REFERER"
></A
><A
NAME="HIDE-USER-AGENT"
></A
->8.5.24. hide-user-agent</H4
+>8.5.25. hide-user-agent</H4
><P
></P
><DIV
><A
NAME="INSPECT-JPEGS"
></A
->8.5.25. inspect-jpegs</H4
+>8.5.26. inspect-jpegs</H4
><P
></P
><DIV
><A
NAME="KILL-POPUPS"
></A
NAME="KILL-POPUP"
></A
></H4
><A
NAME="LIMIT-CONNECT"
></A
->8.5.27. limit-connect</H4
+>8.5.28. limit-connect</H4
><P
></P
><DIV
><A
NAME="PREVENT-COMPRESSION"
></A
->8.5.28. prevent-compression</H4
+>8.5.29. prevent-compression</H4
><P
></P
><DIV
><DD
><P
> More and more websites send their content compressed by default, which
- is generally a good idea and saves bandwidth. But for the <TT
+ is generally a good idea and saves bandwidth. But the <TT
CLASS="LITERAL"
><A
HREF="actions-file.html#FILTER"
HREF="actions-file.html#KILL-POPUPS"
>kill-popups</A
></TT
-> actions to work,
- <SPAN
+> actions need
+ access to the uncompressed data.
+ </P
+><P
+> When compiled with zlib support (available since <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> needs access to the uncompressed data.
- Unfortunately, <SPAN
+> 3.0.7), content that should be
+ filtered is decompressed on-the-fly and you don't have to worry about this action.
+ If you are using an older <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> can't yet(!) uncompress, filter, and
- re-compress the content on the fly. So if you want to ensure that all websites, including
- those that normally compress, can be filtered, you need to use this action.
+> version, or one that hasn't been compiled with zlib
+ support, this action can be used to convince the server to send the content uncompressed.
</P
><P
-> This will slow down transfers from those websites, though. If you use any of the above-mentioned
- actions, you will typically want to use <TT
-CLASS="LITERAL"
->prevent-compression</TT
-> in conjunction
- with them.
+> Most text-based instances compress very well, the size is seldom decreased by less than 50%,
+ for markup-heavy instances like news feeds saving more than 90% of the original size isn't
+ unusual.
+ </P
+><P
+> Not using compression will therefore slow down the transfer, and you should only
+ enable this action if you really need it. As of <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> 3.0.7 it's disabled in all
+ predefined action settings.
</P
><P
> Note that some (rare) ill-configured sites don't handle requests for uncompressed
- documents correctly (they send an empty document body). If you use <TT
+ documents correctly. Broken PHP applications tend to send an empty document body,
+ some IIS versions only send the beginning of the content. If you enable
+ <TT
CLASS="LITERAL"
>prevent-compression</TT
->
- per default, you'll have to add exceptions for those sites. See the example for how to do that.
+> per default, you might want to add
+ exceptions for those sites. See the example for how to do that.
</P
></DD
><DT
{ +prevent-compression }
/ # Match all sites
-# Then maybe make exceptions for ill-behaved sites:
+# Then maybe make exceptions for broken sites:
#
{ -prevent-compression }
- .debianhelp.org
- www.pclinuxonline.com</PRE
+.compusa.com/</PRE
></TD
></TR
></TABLE
><A
NAME="OVERWRITE-LAST-MODIFIED"
></A
->8.5.29. overwrite-last-modified</H4
+>8.5.30. overwrite-last-modified</H4
><P
></P
><DIV
><A
NAME="REDIRECT"
></A
->8.5.30. redirect</H4
+>8.5.31. redirect</H4
><P
></P
><DIV
>Parameter:</DT
><DD
><P
-> Any URL.
+> An absolute URL or a single pcrs command.
</P
></DD
><DT
>Notes:</DT
><DD
><P
-> This action is useful to replace whole documents with ones of your
- choosing. This can be used to enforce safe surfing, or just as a simple
- convenience.
+> Requests to which this action applies are answered with a
+ HTTP redirect to URLs of your choosing. The new URL is
+ either provided as parameter, or derived by applying a
+ single pcrs command to the original URL.
</P
><P
-> You can do the same by combining the actions
+> This action will be ignored if you use it together with
<TT
CLASS="LITERAL"
><A
HREF="actions-file.html#BLOCK"
>block</A
></TT
->,
- <TT
-CLASS="LITERAL"
-><A
-HREF="actions-file.html#HANDLE-AS-IMAGE"
->handle-as-image</A
-></TT
-> and
+>.
+ It can be combined with
<TT
CLASS="LITERAL"
><A
-HREF="actions-file.html#SET-IMAGE-BLOCKER"
->set-image-blocker{URL}</A
+HREF="actions-file.html#FAST-REDIRECTS"
+>fast-redirects{check-decoded-url}</A
></TT
->.
- It doesn't sound right for non-image documents, and that's why this action
- was created.
+>
+ to redirect to a decoded version of a rewritten URL.
</P
><P
-> This action will be ignored if you use it together with
- <TT
-CLASS="LITERAL"
-><A
-HREF="actions-file.html#BLOCK"
->block</A
-></TT
->.
+> Use this action carefully, make sure not to create redirection loops
+ and be aware that using your own redirects might make it
+ possible to fingerprint your requests.
</P
></DD
><DT
CLASS="SCREEN"
># Replace example.com's style sheet with another one
{ +redirect{http://localhost/css-replacements/example.com.css} }
- example.com/stylesheet.css
+ example.com/stylesheet\.css
# Create a short, easy to remember nickname for a favorite site
+# (relies on the browser accept and forward invalid URLs to <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+>)
{ +redirect{http://www.privoxy.org/user-manual/actions-file.html} }
- a</PRE
+ a
+
+# Always use the expanded view for Undeadly.org articles
+# (Note the $ at the end of the URL pattern to make sure
+# the request for the rewritten URL isn't redirected as well)
+{+redirect{s@$@&mode=expanded@}}
+undeadly.org/cgi\?action=article&sid=\d*$</PRE
></TD
></TR
></TABLE
><A
NAME="SEND-VANILLA-WAFER"
></A
->8.5.31. send-vanilla-wafer</H4
+>8.5.32. send-vanilla-wafer</H4
><P
></P
><DIV
><A
NAME="SEND-WAFER"
></A
->8.5.32. send-wafer</H4
+>8.5.33. send-wafer</H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
+NAME="SERVER-HEADER-FILTER"
+></A
+>8.5.34. server-header-filter</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>Typical use:</DT
+><DD
+><P
+> Rewrite or remove single server headers.
+ </P
+></DD
+><DT
+>Effect:</DT
+><DD
+><P
+> All server headers to which this action applies are filtered on-the-fly
+ through the specified regular expression based substitutions.
+ </P
+></DD
+><DT
+>Type:</DT
+><DD
+><P
+>Parameterized.</P
+></DD
+><DT
+>Parameter:</DT
+><DD
+><P
+> The name of a server-header filter, as defined in one of the
+ <A
+HREF="filter-file.html"
+>filter files</A
+>.
+ </P
+></DD
+><DT
+>Notes:</DT
+><DD
+><P
+> Server-header filters are applied to each header on its own, not to
+ all at once. This makes it easier to diagnose problems, but on the downside
+ you can't write filters that only change header x if header y's value is z.
+ You can do that by using tags though.
+ </P
+><P
+> Server-header filters are executed after the other header actions have finished
+ and use their output as input.
+ </P
+><P
+> Please refer to the <A
+HREF="filter-file.html"
+>filter file chapter</A
+>
+ to learn which server-header filters are available by default, and how to
+ create your own.
+ </P
+></DD
+><DT
+>Example usage (section):</DT
+><DD
+><P
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="90%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+>{+server-header-filter{html-to-xml}}
+example.org/xml-instance-that-is-delivered-as-html
+
+{+server-header-filter{xml-to-html}}
+example.org/instance-that-is-delivered-as-xml-but-is-not
+ </PRE
+></TD
+></TR
+></TABLE
+>
+ </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><H4
+CLASS="SECT3"
+><A
+NAME="SERVER-HEADER-TAGGER"
+></A
+>8.5.35. server-header-tagger</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>Typical use:</DT
+><DD
+><P
+> Disable or disable filters based on the Content-Type header.
+ </P
+></DD
+><DT
+>Effect:</DT
+><DD
+><P
+> Server headers to which this action applies are filtered on-the-fly through
+ the specified regular expression based substitutions, the result is used as
+ tag.
+ </P
+></DD
+><DT
+>Type:</DT
+><DD
+><P
+>Parameterized.</P
+></DD
+><DT
+>Parameter:</DT
+><DD
+><P
+> The name of a server-header tagger, as defined in one of the
+ <A
+HREF="filter-file.html"
+>filter files</A
+>.
+ </P
+></DD
+><DT
+>Notes:</DT
+><DD
+><P
+> Server-header taggers are applied to each header on its own,
+ and as the header isn't modified, each tagger <SPAN
+CLASS="QUOTE"
+>"sees"</SPAN
+>
+ the original.
+ </P
+><P
+> Server-header taggers are executed before all other header actions
+ that modify server headers. Their tags can be used to control
+ all of the other server-header actions, the content filters
+ and the crunch actions (<A
+HREF="actions-file.html#REDIRECT"
+>redirect</A
+>
+ and <A
+HREF="actions-file.html#BLOCK"
+>block</A
+>).
+ </P
+><P
+> Obviously crunching based on tags created by server-header taggers
+ doesn't prevent the request from showing up in the server's log file.
+ </P
+></DD
+><DT
+>Example usage (section):</DT
+><DD
+><P
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="90%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+># Tag every request with the declared content type
+{+client-header-filter{content-type}}
+/
+ </PRE
+></TD
+></TR
+></TABLE
+>
+ </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><H4
+CLASS="SECT3"
+><A
NAME="SESSION-COOKIES-ONLY"
></A
->8.5.33. session-cookies-only</H4
+>8.5.36. session-cookies-only</H4
><P
></P
><DIV
><A
NAME="SET-IMAGE-BLOCKER"
></A
->8.5.34. set-image-blocker</H4
+>8.5.37. set-image-blocker</H4
><P
></P
><DIV
>
</P
><P
-> Redirect to the BSD devil:
+> Redirect to the BSD daemon:
</P
><P
> <TABLE
><A
NAME="TREAT-FORBIDDEN-CONNECTS-LIKE-BLOCKS"
></A
->8.5.35. treat-forbidden-connects-like-blocks</H4
+>8.5.38. treat-forbidden-connects-like-blocks</H4
><P
></P
><DIV
<SPAN
CLASS="QUOTE"
>"Go there anyway"</SPAN
-> link becomes rather useless:
- it lets the client request the home page of the forbidden host
- through unencrypted HTTP, still using the port of the last request.
- </P
-><P
-> If you previously configured <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> to do the
- request through a SSL tunnel, everything will work. Most likely you haven't
- and the server will respond with an error message because it is expecting
- HTTPS (SSL).
+> wouldn't work and is therefore suppressed.
</P
></DD
><DT
><H3
CLASS="SECT3"
><A
-NAME="AEN3952"
+NAME="AEN4122"
></A
->8.5.36. Summary</H3
+>8.5.39. Summary</H3
><P
> Note 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
><H3
CLASS="SECT3"
><A
-NAME="AEN4017"
+NAME="AEN4187"
></A
>8.7.1. default.action</H3
><P
-<A
HREF="actions-file.html#ADD-HEADER"
>add-header</A
+> \
+ -<A
+HREF="actions-file.html#CLIENT-HEADER-FILTER"
+>client-header-filter{hide-tor-exit-notation}</A
> \
-<A
HREF="actions-file.html#BLOCK"
>filter{ie-exploits}</A
> \
-<A
-HREF="actions-file.html#FILTER-CLIENT-HEADERS"
->filter-client-headers</A
-> \
- -<A
-HREF="actions-file.html#FILTER-SERVER-HEADERS"
->filter-server-headers</A
-> \
- -<A
HREF="actions-file.html#FILTER-GOOGLE"
->filter-google</A
+>filter{google}</A
> \
-<A
HREF="actions-file.html#FILTER-YAHOO"
->filter-yahoo</A
+>filter{yahoo}</A
> \
-<A
HREF="actions-file.html#FILTER-MSN"
->filter-msn</A
+>filter{msn}</A
> \
-<A
HREF="actions-file.html#FILTER-BLOGSPOT"
->filter-blogspot</A
-> \
- -<A
-HREF="actions-file.html#FILTER-XML-TO-HTML"
->filter-xml-to-html</A
-> \
- -<A
-HREF="actions-file.html#FILTER-HTML-TO-XML"
->filter-html-to-xml</A
+>filter{blogspot}</A
> \
-<A
HREF="actions-file.html#FILTER-NO-PING"
->filter-no-ping</A
-> \
- -<A
-HREF="actions-file.html#FILTER-HIDE-TOR-EXIT-NOTATION"
->filter-hide-tor-exit-notation</A
+>filter{no-ping}</A
> \
-<A
HREF="actions-file.html#FORCE-TEXT-MODE"
-<A
HREF="actions-file.html#SEND-WAFER"
>send-wafer</A
+> \
+ -<A
+HREF="actions-file.html#SERVER-HEADER-FILTER"
+>server-header-filter{xml-to-html}</A
+> \
+ -<A
+HREF="actions-file.html#SERVER-HEADER-FILTER"
+>server-header-filter{html-to-xml}</A
> \
+<A
HREF="actions-file.html#SESSION-COOKIES-ONLY"
><H3
CLASS="SECT3"
><A
-NAME="AEN4206"
+NAME="AEN4374"
></A
>8.7.2. user.action</H3
><P
HREF="actions-file.html#BLOCK"
>block</A
> }
- www.example.com/nasty-ads/sponsor.gif
+ www.example.com/nasty-ads/sponsor\.gif
another.popular.site.net/more/junk/here/</PRE
></TD
></TR
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.6 User Manual"
+TITLE="Privoxy 3.0.7 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="See Also"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.6 User Manual</TH
+>Privoxy 3.0.7 User Manual</TH
></TR
><TR
><TD
><H2
CLASS="SECT2"
><A
-NAME="AEN5046"
+NAME="AEN5252"
></A
>14.2. Privoxy's Internal Pages</H2
><P
Privoxy main page:
</P
><A
-NAME="AEN5060"
+NAME="AEN5266"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
editing of actions files:
</P
><A
-NAME="AEN5068"
+NAME="AEN5274"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
Show the source code version numbers:
</P
><A
-NAME="AEN5073"
+NAME="AEN5279"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
Show the browser's request headers:
</P
><A
-NAME="AEN5078"
+NAME="AEN5284"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
Show which actions apply to a URL and why:
</P
><A
-NAME="AEN5083"
+NAME="AEN5289"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
to run, but only as a pass-through proxy, with no actions taking place:
</P
><A
-NAME="AEN5089"
+NAME="AEN5295"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
> Short cuts. Turn off, then on:
</P
><A
-NAME="AEN5093"
+NAME="AEN5299"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
</P
></BLOCKQUOTE
><A
-NAME="AEN5096"
+NAME="AEN5302"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
{-add-header
-block
+ -client-header-filter{hide-tor-exit-notation}
-content-type-overwrite
-crunch-client-header
-crunch-if-none-match
-filter {yahoo}
-filter {msn}
-filter {blogspot}
- -filter {xml-to-html}
- -filter {html-to-xml}
-filter {no-ping}
- -filter{hide-tor-exit-notation}
- -filter-client-headers
- -filter-server-headers
-force-text-mode
-handle-as-empty-document
-handle-as-image
-redirect
-send-vanilla-wafer
-send-wafer
+ -server-header-filter{xml-to-html}
+ -server-header-filter{html-to-xml}
+session-cookies-only
+set-image-blocker {pattern}
-treat-forbidden-connects-like-blocks }
-add-header
-block
+ -client-header-filter{hide-tor-exit-notation}
-content-type-overwrite
-crunch-client-header
-crunch-if-none-match
-filter {yahoo}
-filter {msn}
-filter {blogspot}
- -filter {xml-to-html}
- -filter {html-to-xml}
-filter {no-ping}
- -filter{hide-tor-exit-notation}
- -filter-client-headers
- -filter-server-headers
-force-text-mode
-handle-as-empty-document
-handle-as-image
-redirect
-send-vanilla-wafer
-send-wafer
+ -server-header-filter{xml-to-html}
+ -server-header-filter{html-to-xml}
-session-cookies-only
+set-image-blocker {pattern}
-treat-forbidden-connects-like-blocks </PRE
{-add-header
-block
+ -client-header-filter{hide-tor-exit-notation}
-content-type-overwrite
-crunch-client-header
-crunch-if-none-match
-filter {yahoo}
-filter {msn}
-filter {blogspot}
- -filter {xml-to-html}
- -filter {html-to-xml}
-filter {no-ping}
- -filter{hide-tor-exit-notation}
- -filter-client-headers
- -filter-server-headers
-force-text-mode
-handle-as-empty-document
-handle-as-image
+prevent-compression
-redirect
-send-vanilla-wafer
- -send-wafer
+ -send-wafer
+ -server-header-filter{xml-to-html}
+ -server-header-filter{html-to-xml}
+session-cookies-only
+set-image-blocker{blank}
-treat-forbidden-connects-like-blocks }
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.6 User Manual"
+TITLE="Privoxy 3.0.7 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Privoxy Configuration"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.6 User Manual</TH
+>Privoxy 3.0.7 User Manual</TH
></TR
><TR
><TD
><H4
CLASS="SECT3"
><A
+NAME="TEMPLDIR"
+></A
+>7.2.2. templdir</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>Specifies:</DT
+><DD
+><P
+>An alternative directory where the templates are loaded from</P
+></DD
+><DT
+>Type of value:</DT
+><DD
+><P
+>Path name</P
+></DD
+><DT
+>Default value:</DT
+><DD
+><P
+>unset</P
+></DD
+><DT
+>Effect if unset:</DT
+><DD
+><P
+>The templates are assumed to be located in confdir/template.</P
+></DD
+><DT
+>Notes:</DT
+><DD
+><P
+> Privoxy's original templates are usually overwritten
+ with each update. Use this option to relocate customized templates
+ that should be kept. Note that you might be missing new features
+ if you use outdated templates.
+ </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><H4
+CLASS="SECT3"
+><A
NAME="LOGDIR"
></A
->7.2.2. logdir</H4
+>7.2.3. logdir</H4
><P
></P
><DIV
><A
NAME="ACTIONSFILE"
></A
->7.2.3. actionsfile</H4
+>7.2.4. actionsfile</H4
><A
NAME="DEFAULT.ACTION"
></A
>Type of value:</DT
><DD
><P
->File name, relative to <TT
+>Complete file name, relative to <TT
CLASS="LITERAL"
>confdir</TT
->, without the <TT
-CLASS="LITERAL"
->.action</TT
-> suffix</P
+></P
></DD
><DT
>Default values:</DT
><TD
> <P
CLASS="LITERALLAYOUT"
-> standard # Internal purposes, no editing recommended</P
+> standard.action # Internal purposes, no editing recommended</P
>
</TD
></TR
><TD
> <P
CLASS="LITERALLAYOUT"
-> default # Main actions file</P
+> default.action # Main actions file</P
>
</TD
></TR
><TD
> <P
CLASS="LITERALLAYOUT"
-> user # User customizations</P
+> user.action # User customizations</P
>
</TD
></TR
>Effect if unset:</DT
><DD
><P
-> No actions are taken at all. Simple neutral proxying.
+> No actions are taken at all. More or less neutral proxying.
</P
></DD
><DT
> without at
least one actions file.
</P
+><P
+> Note that since Privoxy 3.0.7, the complete filename, including the <SPAN
+CLASS="QUOTE"
+>".action"</SPAN
+>
+ extension has to be specified. The syntax change was necessary to be consistent
+ with the other file options and to allow previously forbidden characters.
+ </P
></DD
></DL
></DIV
><A
NAME="FILTERFILE"
></A
->7.2.4. filterfile</H4
+>7.2.5. filterfile</H4
><A
NAME="DEFAULT.FILTER"
></A
><A
NAME="LOGFILE"
></A
->7.2.5. logfile</H4
+>7.2.6. logfile</H4
><P
></P
><DIV
><A
NAME="JARFILE"
></A
->7.2.6. jarfile</H4
+>7.2.7. jarfile</H4
><P
></P
><DIV
><A
NAME="TRUSTFILE"
></A
->7.2.7. trustfile</H4
+>7.2.8. trustfile</H4
><P
></P
><DIV
debug 2 # show each connection status
debug 4 # show I/O status
debug 8 # show header parsing
- debug 16 # log all data into the logfile
+ debug 16 # log all data written to the network into the logfile
debug 32 # debug force feature
- debug 64 # debug regular expression filter
- debug 128 # debug fast redirects
+ debug 64 # debug regular expression filters
+ debug 128 # debug redirects
debug 256 # debug GIF de-animation
debug 512 # Common Log Format
debug 1024 # debug kill pop-ups
CLASS="EMPHASIS"
>fatal</I
></SPAN
-> errors (i.e. ones which crash
+> errors (i.e. ones which causes
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->) is always on and cannot be disabled.
+> to exit) is always on and cannot be disabled.
</P
><P
> If you want to use CLF (Common Log Format), you should set <SPAN
></SPAN
> and not enable anything else.
</P
+><P
+> <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> has a hard-coded limit for the
+ length of log messages. If it's reached, messages are logged truncated
+ and marked with <SPAN
+CLASS="QUOTE"
+>"... [too long, truncated]"</SPAN
+>.
+ </P
></DD
></DL
></DIV
<SPAN
CLASS="QUOTE"
>"toggled off"</SPAN
-> mode, i.e. behave like a normal, content-neutral
- proxy where all ad blocking, filtering, etc are disabled. See
+> mode, i.e. mostly behave like a normal,
+ content-neutral proxy where all ad blocking, filtering, etc are disabled. See
<TT
CLASS="LITERAL"
>enable-remote-toggle</TT
> When toggled off, <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> acts like a normal,
+> mostly acts like a normal,
content-neutral proxy, i.e. it acts as if none of the actions applied to
any URL.
</P
><H4
CLASS="SECT3"
><A
+NAME="ENFORCE-BLOCKS"
+></A
+>7.4.6. enforce-blocks</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>Specifies:</DT
+><DD
+><P
+> Whether the user is allowed to ignore blocks and can <SPAN
+CLASS="QUOTE"
+>"go there anyway"</SPAN
+>.
+ </P
+></DD
+><DT
+>Type of value:</DT
+><DD
+><P
+> <TT
+CLASS="REPLACEABLE"
+><I
+>0 or 1</I
+></TT
+>
+ </P
+></DD
+><DT
+>Default value:</DT
+><DD
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>0</I
+></SPAN
+></P
+></DD
+><DT
+>Effect if unset:</DT
+><DD
+><P
+> Blocks are not enforced.
+ </P
+></DD
+><DT
+>Notes:</DT
+><DD
+><P
+> <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> is mainly used to block and filter
+ requests as a service to the user, for example to block ads and other
+ junk that clogs the pipes. <SPAN
+CLASS="APPLICATION"
+>Privoxy's</SPAN
+> configuration
+ isn't perfect and sometimes innocent pages are blocked. In this situation it
+ makes sense to allow the user to enforce the request and have
+ <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> ignore the block.
+ </P
+><P
+> In the default configuration <SPAN
+CLASS="APPLICATION"
+>Privoxy's</SPAN
+>
+ <SPAN
+CLASS="QUOTE"
+>"Blocked"</SPAN
+> page contains a <SPAN
+CLASS="QUOTE"
+>"go there anyway"</SPAN
+>
+ link to adds a special string (the force prefix) to the request URL.
+ If that link is used, <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> will
+ detect the force prefix, remove it again and let the request pass.
+ </P
+><P
+> Of course <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> can also be used to enforce
+ a network policy. In that case the user obviously should not be able to
+ bypass any blocks, and that's what the <SPAN
+CLASS="QUOTE"
+>"enforce-blocks"</SPAN
+>
+ option is for. If it's enabled, <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> hides
+ the <SPAN
+CLASS="QUOTE"
+>"go there anyway"</SPAN
+> link. If the user adds the force
+ prefix by hand, it will not be accepted and the circumvention attempt
+ is logged.
+ </P
+></DD
+><DT
+>Examples:</DT
+><DD
+><P
+> enforce-blocks 1
+ </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><H4
+CLASS="SECT3"
+><A
NAME="ACLS"
></A
->7.4.6. ACLs: permit-access and deny-access</H4
+>7.4.7. ACLs: permit-access and deny-access</H4
><A
NAME="PERMIT-ACCESS"
></A
</P
><P
> Multiple ACL lines are OK.
- If any ACLs are specified, then the <SPAN
+ If any ACLs are specified, <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->
- talks only to IP addresses that match at least one <TT
+> only talks
+ to IP addresses that match at least one <TT
CLASS="LITERAL"
>permit-access</TT
> line
</P
><P
> Denying access to particular sites by ACL may have undesired side effects
- if the site in question is hosted on a machine which also hosts other sites.
+ if the site in question is hosted on a machine which also hosts other sites
+ (most sites are).
</P
></DD
><DT
</P
><P
> Allow any host on the same class C subnet as www.privoxy.org access to
- nothing but www.example.com:
+ nothing but www.example.com (or other domains hosted on the same system):
</P
><P
> <TABLE
</P
><P
> Allow access from any host on the 26-bit subnet 192.168.45.64 to anywhere,
- with the exception that 192.168.45.73 may not access www.dirty-stuff.example.com:
+ with the exception that 192.168.45.73 may not access the IP address behind
+ www.dirty-stuff.example.com:
</P
><P
> <TABLE
><A
NAME="BUFFER-LIMIT"
></A
->7.4.7. buffer-limit</H4
+>7.4.8. buffer-limit</H4
><P
></P
><DIV
>7.5. Forwarding</H2
><P
> This feature allows routing of HTTP requests through a chain of
- multiple proxies.
- It can be used to better protect privacy and confidentiality when
- accessing specific domains by routing requests to those domains
- through an anonymous public proxy. Or to use a caching proxy to speed up browsing. Or chaining to a parent
- proxy may be necessary because the machine that <SPAN
+ multiple proxies.</P
+><P
+> Forwarding can be used to chain Privoxy with a caching proxy to speed
+ up browsing. Using a parent proxy may also be necessary if the machine
+ that <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
+> runs on has no direct Internet access.</P
+><P
+> Note that parent proxies can severely decrease your privacy level.
+ For example a parent proxy could add your IP address to the request
+ headers and if it's a caching proxy it may add the <SPAN
+CLASS="QUOTE"
+>"Etag"</SPAN
>
- runs on has no direct Internet access.</P
+ header to revalidation requests again, even though you configured Privoxy
+ to remove it. It may also ignore Privoxy's header time randomization and use the
+ original values which could be used by the server as cookie replacement
+ to track your steps between visits.</P
><P
> Also specified here are SOCKS proxies. <SPAN
CLASS="APPLICATION"
>Examples:</DT
><DD
><P
-> Everything goes to an example anonymizing proxy, except SSL on port 443 (which it doesn't handle):
+> Everything goes to an example parent proxy, except SSL on port 443 (which it doesn't handle):
</P
><P
> <TABLE
><TD
><PRE
CLASS="SCREEN"
-> forward / anon-proxy.example.org:8080
+> forward / parent-proxy.example.org:8080
forward :443 .</PRE
></TD
></TR
>Specifies:</DT
><DD
><P
-> Through which SOCKS proxy (and to which parent HTTP proxy) specific requests should be routed.
+> Through which SOCKS proxy (and optionally to which parent HTTP proxy) specific requests should be routed.
</P
></DD
><DT
>Effect if unset:</DT
><DD
><P
-> Forwarded connections are treated like direct connections and no retry attempts are made.
+> Connections forwarded through other proxies are treated like direct connections and no retry attempts are made.
</P
></DD
><DT
>forwarded-connect-retries</I
></TT
> is mainly interesting
- for socks4a connections, where Privoxy can't detect why the connections failed.
+ for socks4a connections, where <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> can't detect why the connections failed.
The connection might have failed because of a DNS timeout in which case a retry makes sense,
but it might also have failed because the server doesn't exist or isn't reachable. In this
case the retry will just delay the appearance of Privoxy's error message.
</P
><P
+> Note that in the context of this option, <SPAN
+CLASS="QUOTE"
+>"forwarded connections"</SPAN
+> includes all connections
+ that Privoxy forwards through other proxies. This option is not limited to the HTTP CONNECT method.
+ </P
+><P
> Only use this option, if you are getting many forwarding related error messages,
that go away when you try again manually. Start with a small value and check Privoxy's
logfile from time to time, to see how many retries are usually needed.
></DL
></DIV
></DIV
+><DIV
+CLASS="SECT3"
+><H4
+CLASS="SECT3"
+><A
+NAME="ACCEPT-INTERCEPTED-REQUESTS"
+></A
+>7.5.5. accept-intercepted-requests</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>Specifies:</DT
+><DD
+><P
+> Whether intercepted requests should be treated as valid.
+ </P
+></DD
+><DT
+>Type of value:</DT
+><DD
+><P
+> <TT
+CLASS="REPLACEABLE"
+><I
+>0 or 1</I
+></TT
+>
+ </P
+></DD
+><DT
+>Default value:</DT
+><DD
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>0</I
+></SPAN
+></P
+></DD
+><DT
+>Effect if unset:</DT
+><DD
+><P
+> Only proxy requests are accepted, intercepted requests are treated as invalid.
+ </P
+></DD
+><DT
+>Notes:</DT
+><DD
+><P
+> If you don't trust your clients and want to force them
+ to use <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+>, enable this
+ option and configure your packet filter to redirect outgoing
+ HTTP connections into <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+>.
+ </P
+><P
+> Make sure that <SPAN
+CLASS="APPLICATION"
+>Privoxy's</SPAN
+> own requests
+ aren't redirected as well. Additionally take care that
+ <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> can't intentionally connect
+ to itself, otherwise you could run into redirection loops if
+ <SPAN
+CLASS="APPLICATION"
+>Privoxy's</SPAN
+> listening port is reachable
+ by the outside or an attacker has access to the pages you visit.
+ </P
+></DD
+><DT
+>Examples:</DT
+><DD
+><P
+> accept-intercepted-requests 1
+ </P
+></DD
+></DL
+></DIV
+></DIV
+><DIV
+CLASS="SECT3"
+><H4
+CLASS="SECT3"
+><A
+NAME="SPLIT-LARGE-FORMS"
+></A
+>7.5.6. split-large-forms</H4
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+>Specifies:</DT
+><DD
+><P
+> Whether the CGI interface should stay compatible with broken HTTP clients.
+ </P
+></DD
+><DT
+>Type of value:</DT
+><DD
+><P
+> <TT
+CLASS="REPLACEABLE"
+><I
+>0 or 1</I
+></TT
+>
+ </P
+></DD
+><DT
+>Default value:</DT
+><DD
+><P
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>0</I
+></SPAN
+></P
+></DD
+><DT
+>Effect if unset:</DT
+><DD
+><P
+> The CGI form generate long GET URLs.
+ </P
+></DD
+><DT
+>Notes:</DT
+><DD
+><P
+> <SPAN
+CLASS="APPLICATION"
+>Privoxy's</SPAN
+> CGI forms can lead to
+ rather long URLs. This isn't a problem as far as the HTTP
+ standard is concerned, but it can confuse clients with arbitrary
+ URL lenght limitations.
+ </P
+><P
+> Enabling split-large-forms causes <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+>
+ to devide big forms into smaller ones to keep the URL length down.
+ It makes editing a lot less convenient and you can no longer
+ submit all changes at once, but at least it works around this
+ browser bug.
+ </P
+><P
+> If you don't notice any editing problems, there is no reason
+ to enable this option, but if one of the submit buttons appears
+ to be broken, you should give it a try.
+ </P
+></DD
+><DT
+>Examples:</DT
+><DD
+><P
+> split-large-forms 1
+ </P
+></DD
+></DL
+></DIV
+></DIV
></DIV
><DIV
CLASS="SECT2"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.6 User Manual"
+TITLE="Privoxy 3.0.7 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Starting Privoxy"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.6 User Manual</TH
+>Privoxy 3.0.7 User Manual</TH
></TR
><TR
><TD
><H2
CLASS="SECT2"
><A
-NAME="AEN841"
+NAME="AEN755"
></A
>6.1. Controlling Privoxy with Your Web Browser</H2
><P
> <H2
CLASS="BRIDGEHEAD"
><A
-NAME="AEN849"
+NAME="AEN763"
></A
> Privoxy Menu</H2
><P
><TR
><TD
> ▪ <A
-HREF="http://www.privoxy.org/ 3.0.6/user-manual/"
+HREF="http://www.privoxy.org/ 3.0.7/user-manual/"
TARGET="_top"
>Documentation</A
>
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.6 User Manual"
+TITLE="Privoxy 3.0.7 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Privoxy's Template Files"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.6 User Manual</TH
+>Privoxy 3.0.7 User Manual</TH
></TR
><TR
><TD
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.6 User Manual"
+TITLE="Privoxy 3.0.7 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Contacting the Developers, Bug Reporting and Feature
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.6 User Manual</TH
+>Privoxy 3.0.7 User Manual</TH
></TR
><TR
><TD
><H2
CLASS="SECT2"
><A
-NAME="AEN4796"
+NAME="AEN4997"
></A
>12.1. License</H2
><P
<br>
Hal Burgiss<br>
Ian Cummings<br>
+ Justin McMurtry<br>
Roland Rosenfeld</P
><P
> Former Privoxy Team Members:</P
Jindrich Makovicka <br>
David Mediavilla <br>
Raphael Moll<br>
+ Adam Piggott<br>
Oliver Stoeneberg<br>
Martin Thomas<br>
Roberto Ragusa<br>
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.6 User Manual"
+TITLE="Privoxy 3.0.7 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Actions Files"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.6 User Manual</TH
+>Privoxy 3.0.7 User Manual</TH
></TR
><TR
><TD
></A
>9. Filter Files</H1
><P
-> On-the-fly text substitutions that can be invoked through the
- <TT
-CLASS="LITERAL"
-><A
-HREF="actions-file.html#FILTER"
->filter</A
-></TT
-> action need
+> On-the-fly text substitutions need
to be defined in a <SPAN
CLASS="QUOTE"
>"filter file"</SPAN
can then be invoked as an <SPAN
CLASS="QUOTE"
>"action"</SPAN
->. Multiple filter files can be
- defined through the <TT
+>.</P
+><P
+> <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> supports three different filter actions:
+ <TT
+CLASS="LITERAL"
+><A
+HREF="actions-file.html#FILTER"
+>filter</A
+></TT
+> to
+ rewrite the content that is send to the client,
+ <TT
+CLASS="LITERAL"
+><A
+HREF="actions-file.html#CLIENT-HEADER-FILTER"
+>client-header-filter</A
+></TT
+>
+ to rewrite headers that are send by the client, and
+ <TT
+CLASS="LITERAL"
+><A
+HREF="actions-file.html#SERVER-HEADER-FILTER"
+>server-header-filter</A
+></TT
+>
+ to rewrite headers that are send by the server, and</P
+><P
+> <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> also supports two tagger actions:
+ <TT
+CLASS="LITERAL"
+><A
+HREF="actions-file.html#CLIENT-HEADER-TAGGER"
+>client-header-tagger</A
+></TT
+>
+ and
+ <TT
+CLASS="LITERAL"
+><A
+HREF="actions-file.html#SERVER-HEADER-TAGGER"
+>server-header-tagger</A
+></TT
+>.
+ Taggers and filters use the same syntax in the filter files, the differnce
+ is that taggers don't modify the text they are filtering, but use a rewritten
+ version of the filtered text as tag. The tags can then be used to change the
+ applying actions through sections with <A
+HREF="actions-file.html#TAG-PATTERN"
+>tag-patterns</A
+>.</P
+><P
+> Multiple filter files can be defined through the <TT
CLASS="LITERAL"
> <A
HREF="config.html#FILTERFILE"
>.
</P
><P
-> Typical reasons for doing these kinds of substitutions are to eliminate
- common annoyances in HTML and JavaScript, such as pop-up windows,
+> Command tasks for content filters are to eliminate common annoyances in
+ HTML and JavaScript, such as pop-up windows,
exit consoles, crippled windows without navigation tools, the
infamous <BLINK> tag etc, to suppress images with certain
width and height attributes (standard banner sizes or web-bugs),
- or just to have fun. The possibilities are endless.</P
+ or just to have fun.</P
><P
-> Filtering works on any text-based document type, including
+> Content filtering works on any text-based document type, including
HTML, JavaScript, CSS etc. (all <TT
CLASS="LITERAL"
>text/*</TT
>"roll
your own"</SPAN
> filters, you should first be familiar with HTML syntax,
- and, of course, regular expressions. By default, filters are only applied
- to the raw document content, but can be extended to the HTTP headers with
- the supplemental actions:
- <A
-HREF="actions-file.html#FILTER-CLIENT-HEADERS"
->filter-client-headers</A
-> and
- <A
-HREF="actions-file.html#FILTER-SERVER-HEADERS"
->filter-server-headers</A
->.</P
+ and, of course, regular expressions.</P
><P
> Just like the <A
HREF="actions-file.html"
>filters</I
></SPAN
>
- here. Each filter consists of a heading line, that starts with the
+ here. Each filter consists of a heading line, that starts with one of the
<SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
->keyword</I
+>keywords</I
></SPAN
> <TT
CLASS="LITERAL"
>FILTER:</TT
->, followed by
- the filter's <SPAN
+>,
+ <TT
+CLASS="LITERAL"
+>CLIENT-HEADER-FILTER:</TT
+> or <TT
+CLASS="LITERAL"
+>SERVER-HEADER-FILTER:</TT
+>
+ followed by the filter's <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>actions file</A
>.</P
><P
-> A filter header line for a filter called <SPAN
+> Filter definitions start with a header line that contains the filter
+ type, the filter name and the filter description.
+ A content filter header line for a filter called <SPAN
CLASS="QUOTE"
>"foo"</SPAN
> could look
><H2
CLASS="SECT2"
><A
-NAME="AEN4346"
+NAME="AEN4528"
></A
>9.1. Filter File Tutorial</H2
><P
> Now, let's complete our <SPAN
CLASS="QUOTE"
>"foo"</SPAN
-> filter. We have already defined
+> content filter. We have already defined
the heading, but the jobs are still missing. Since all it does is to replace
<SPAN
CLASS="QUOTE"
></DT
><DD
><P
-> Header filter to change the Content-Type from xml to html.
+> Server-header filter to change the Content-Type from xml to html.
</P
></DD
><DT
></DT
><DD
><P
-> Header filter to change the Content-Type from html to xml.
+> Server-header filter to change the Content-Type from html to xml.
</P
></DD
><DT
></DT
><DD
><P
-> Header filter to remove the <B
+> Client-header filter to remove the <B
CLASS="COMMAND"
>Tor</B
> exit node notation
found in Host and Referer headers.
</P
+><P
+> If <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> and <B
+CLASS="COMMAND"
+>Tor</B
+> are chained and <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+>
+ is configured to use socks4a, one can use <SPAN
+CLASS="QUOTE"
+>"http://www.example.org.foobar.exit/"</SPAN
+>
+ to access the host <SPAN
+CLASS="QUOTE"
+>"www.example.org"</SPAN
+> through the
+ <B
+CLASS="COMMAND"
+>Tor</B
+> exit node <SPAN
+CLASS="QUOTE"
+>"foobar"</SPAN
+>.
+ </P
+><P
+> As the HTTP client isn't aware of this notation, it treats the
+ whole string <SPAN
+CLASS="QUOTE"
+>"www.example.org.foobar.exit"</SPAN
+> as host and uses it
+ for the <SPAN
+CLASS="QUOTE"
+>"Host"</SPAN
+> and <SPAN
+CLASS="QUOTE"
+>"Referer"</SPAN
+> headers. From the
+ server's point of view the resulting headers are invalid and can cause problems.
+ </P
+><P
+> An invalid <SPAN
+CLASS="QUOTE"
+>"Referer"</SPAN
+> header can trigger <SPAN
+CLASS="QUOTE"
+>"hot-linking"</SPAN
+>
+ protections, an invalid <SPAN
+CLASS="QUOTE"
+>"Host"</SPAN
+> header will make it impossible for
+ the server to find the right vhost (several domains hosted on the same IP address).
+ </P
+><P
+> This client-header filter removes the <SPAN
+CLASS="QUOTE"
+>"foo.exit"</SPAN
+> part in those headers
+ to prevent the mentioned problems. Note that it only modifies
+ the HTTP headers, it doesn't make it impossible for the server
+ to detect your <B
+CLASS="COMMAND"
+>Tor</B
+> exit node based on the IP address
+ the request is coming from.
+ </P
></DD
></DL
></DIV
<HTML
><HEAD
><TITLE
->Privoxy 3.0.6 User Manual</TITLE
+>Privoxy 3.0.7 User Manual</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
><A
NAME="AEN2"
></A
->Privoxy 3.0.6 User Manual</H1
+>Privoxy 3.0.7 User Manual</H1
><P
CLASS="PUBDATE"
> <SUB
> <A
HREF="copyright.html"
>Copyright</A
-> © 2001 - 2006 by
+> © 2001 - 2007 by
<A
HREF="http://www.privoxy.org/"
TARGET="_top"
><BR></P
><P
CLASS="PUBDATE"
->$Id: user-manual.sgml,v 2.26 2006/10/24 11:16:44 hal9 Exp $<BR></P
+>$Id: user-manual.sgml,v 2.32 2007/06/07 12:36:22 fabiankeil Exp $<BR></P
><DIV
><DIV
CLASS="ABSTRACT"
><DT
>2.1.4. <A
HREF="installation.html#INSTALLATION-PACK-BINTGZ"
->Solaris, NetBSD, FreeBSD, HP-UX</A
+>Solaris, NetBSD, HP-UX</A
></DT
><DT
>2.1.5. <A
></DT
><DT
>2.1.8. <A
+HREF="installation.html#INSTALLATION-TBZ"
+>FreeBSD</A
+></DT
+><DT
+>2.1.9. <A
HREF="installation.html#INSTALLATTION-GENTOO"
>Gentoo</A
></DT
><DL
><DT
>6.1. <A
-HREF="configuration.html#AEN841"
+HREF="configuration.html#AEN755"
>Controlling Privoxy with Your Web Browser</A
></DT
><DT
></DT
><DT
>7.2.2. <A
+HREF="config.html#TEMPLDIR"
+>templdir</A
+></DT
+><DT
+>7.2.3. <A
HREF="config.html#LOGDIR"
>logdir</A
></DT
><DT
HREF="config.html#ACTIONSFILE"
>actionsfile</A
></DT
><DT
HREF="config.html#FILTERFILE"
>filterfile</A
></DT
><DT
HREF="config.html#LOGFILE"
>logfile</A
></DT
><DT
HREF="config.html#JARFILE"
>jarfile</A
></DT
><DT
HREF="config.html#TRUSTFILE"
>trustfile</A
></DT
></DT
><DT
>7.4.6. <A
+HREF="config.html#ENFORCE-BLOCKS"
+>enforce-blocks</A
+></DT
+><DT
+>7.4.7. <A
HREF="config.html#ACLS"
>ACLs: permit-access and deny-access</A
></DT
><DT
HREF="config.html#BUFFER-LIMIT"
>buffer-limit</A
></DT
HREF="config.html#FORWARDED-CONNECT-RETRIES"
>forwarded-connect-retries</A
></DT
+><DT
+>7.5.5. <A
+HREF="config.html#ACCEPT-INTERCEPTED-REQUESTS"
+>accept-intercepted-requests</A
+></DT
+><DT
+>7.5.6. <A
+HREF="config.html#SPLIT-LARGE-FORMS"
+>split-large-forms</A
+></DT
></DL
></DD
><DT
><DL
><DT
>8.1. <A
-HREF="actions-file.html#AEN2102"
+HREF="actions-file.html#AEN2160"
>Finding the Right Mix</A
></DT
><DT
>8.2. <A
-HREF="actions-file.html#AEN2109"
+HREF="actions-file.html#AEN2167"
>How to Edit</A
></DT
><DT
>8.3. <A
HREF="actions-file.html#ACTIONS-APPLY"
->How Actions are Applied to URLs</A
+>How Actions are Applied to Requests</A
></DT
><DT
>8.4. <A
><DL
><DT
>8.4.1. <A
-HREF="actions-file.html#AEN2192"
+HREF="actions-file.html#AEN2250"
>The Domain Pattern</A
></DT
><DT
>8.4.2. <A
-HREF="actions-file.html#AEN2263"
+HREF="actions-file.html#AEN2321"
>The Path Pattern</A
></DT
+><DT
+>8.4.3. <A
+HREF="actions-file.html#TAG-PATTERN"
+>The Tag Pattern</A
+></DT
></DL
></DD
><DT
></DT
><DT
>8.5.3. <A
+HREF="actions-file.html#CLIENT-HEADER-FILTER"
+>client-header-filter</A
+></DT
+><DT
+>8.5.4. <A
+HREF="actions-file.html#CLIENT-HEADER-TAGGER"
+>client-header-tagger</A
+></DT
+><DT
+>8.5.5. <A
HREF="actions-file.html#CONTENT-TYPE-OVERWRITE"
>content-type-overwrite</A
></DT
><DT
HREF="actions-file.html#CRUNCH-CLIENT-HEADER"
>crunch-client-header</A
></DT
><DT
HREF="actions-file.html#CRUNCH-IF-NONE-MATCH"
>crunch-if-none-match</A
></DT
><DT
HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
>crunch-incoming-cookies</A
></DT
><DT
HREF="actions-file.html#CRUNCH-SERVER-HEADER"
>crunch-server-header</A
></DT
><DT
HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
>crunch-outgoing-cookies</A
></DT
><DT
HREF="actions-file.html#DEANIMATE-GIFS"
>deanimate-gifs</A
></DT
><DT
HREF="actions-file.html#DOWNGRADE-HTTP-VERSION"
>downgrade-http-version</A
></DT
><DT
HREF="actions-file.html#FAST-REDIRECTS"
>fast-redirects</A
></DT
><DT
HREF="actions-file.html#FILTER"
>filter</A
></DT
><DT
->8.5.13. <A
-HREF="actions-file.html#FILTER-CLIENT-HEADERS"
->filter-client-headers</A
-></DT
-><DT
->8.5.14. <A
-HREF="actions-file.html#FILTER-SERVER-HEADERS"
->filter-server-headers</A
-></DT
-><DT
>8.5.15. <A
HREF="actions-file.html#FORCE-TEXT-MODE"
>force-text-mode</A
></DT
><DT
>8.5.16. <A
+HREF="actions-file.html#FORWARD-OVERRIDE"
+>forward-override</A
+></DT
+><DT
+>8.5.17. <A
HREF="actions-file.html#HANDLE-AS-EMPTY-DOCUMENT"
>handle-as-empty-document</A
></DT
><DT
HREF="actions-file.html#HANDLE-AS-IMAGE"
>handle-as-image</A
></DT
><DT
HREF="actions-file.html#HIDE-ACCEPT-LANGUAGE"
>hide-accept-language</A
></DT
><DT
HREF="actions-file.html#HIDE-CONTENT-DISPOSITION"
>hide-content-disposition</A
></DT
><DT
HREF="actions-file.html#HIDE-IF-MODIFIED-SINCE"
>hide-if-modified-since</A
></DT
><DT
HREF="actions-file.html#HIDE-FORWARDED-FOR-HEADERS"
>hide-forwarded-for-headers</A
></DT
><DT
HREF="actions-file.html#HIDE-FROM-HEADER"
>hide-from-header</A
></DT
><DT
HREF="actions-file.html#HIDE-REFERRER"
>hide-referrer</A
></DT
><DT
HREF="actions-file.html#HIDE-USER-AGENT"
>hide-user-agent</A
></DT
><DT
HREF="actions-file.html#INSPECT-JPEGS"
>inspect-jpegs</A
></DT
><DT
HREF="actions-file.html#KILL-POPUPS"
>kill-popups<A
NAME="KILL-POPUP"
></A
></DT
><DT
HREF="actions-file.html#LIMIT-CONNECT"
>limit-connect</A
></DT
><DT
HREF="actions-file.html#PREVENT-COMPRESSION"
>prevent-compression</A
></DT
><DT
HREF="actions-file.html#OVERWRITE-LAST-MODIFIED"
>overwrite-last-modified</A
></DT
><DT
HREF="actions-file.html#REDIRECT"
>redirect</A
></DT
><DT
HREF="actions-file.html#SEND-VANILLA-WAFER"
>send-vanilla-wafer</A
></DT
><DT
HREF="actions-file.html#SEND-WAFER"
>send-wafer</A
></DT
><DT
->8.5.33. <A
+>8.5.34. <A
+HREF="actions-file.html#SERVER-HEADER-FILTER"
+>server-header-filter</A
+></DT
+><DT
+>8.5.35. <A
+HREF="actions-file.html#SERVER-HEADER-TAGGER"
+>server-header-tagger</A
+></DT
+><DT
+>8.5.36. <A
HREF="actions-file.html#SESSION-COOKIES-ONLY"
>session-cookies-only</A
></DT
><DT
HREF="actions-file.html#SET-IMAGE-BLOCKER"
>set-image-blocker</A
></DT
><DT
HREF="actions-file.html#TREAT-FORBIDDEN-CONNECTS-LIKE-BLOCKS"
>treat-forbidden-connects-like-blocks</A
></DT
><DT
-HREF="actions-file.html#AEN3952"
+HREF="actions-file.html#AEN4122"
>Summary</A
></DT
></DL
><DL
><DT
>8.7.1. <A
-HREF="actions-file.html#AEN4017"
+HREF="actions-file.html#AEN4187"
>default.action</A
></DT
><DT
>8.7.2. <A
-HREF="actions-file.html#AEN4206"
+HREF="actions-file.html#AEN4374"
>user.action</A
></DT
></DL
><DL
><DT
>9.1. <A
-HREF="filter-file.html#AEN4346"
+HREF="filter-file.html#AEN4528"
>Filter File Tutorial</A
></DT
><DT
><DL
><DT
>12.1. <A
-HREF="copyright.html#AEN4796"
+HREF="copyright.html#AEN4997"
>License</A
></DT
><DT
></DT
><DT
>14.2. <A
-HREF="appendix.html#AEN5046"
+HREF="appendix.html#AEN5252"
>Privoxy's Internal Pages</A
></DT
><DD
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.6 User Manual"
+TITLE="Privoxy 3.0.7 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Introduction"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.6 User Manual</TH
+>Privoxy 3.0.7 User Manual</TH
></TR
><TR
><TD
><P
> RPMs can be installed with <TT
CLASS="LITERAL"
->rpm -Uvh privoxy-3.0.6-1.rpm</TT
+>rpm -Uvh privoxy-3.0.7-1.rpm</TT
>,
and will use <TT
CLASS="FILENAME"
> If you have problems with failed dependencies, try rebuilding the SRC RPM:
<TT
CLASS="LITERAL"
->rpm --rebuild privoxy-3.0.6-1.src.rpm</TT
+>rpm --rebuild privoxy-3.0.7-1.src.rpm</TT
>. This
will use your locally installed libraries and RPM version. </P
><P
><A
NAME="INSTALLATION-PACK-BINTGZ"
></A
->2.1.4. Solaris, NetBSD, FreeBSD, HP-UX</H3
+>2.1.4. Solaris, NetBSD, HP-UX</H3
><P
> Create a new directory, <TT
CLASS="LITERAL"
><H3
CLASS="SECT3"
><A
+NAME="INSTALLATION-TBZ"
+></A
+>2.1.8. FreeBSD</H3
+><P
+> Privoxy is part of FreeBSD's Ports Collection, you can build and install
+ it with <TT
+CLASS="LITERAL"
+>cd /usr/ports/www/privoxy; make install clean</TT
+>.</P
+><P
+> If you don't use the ports, you can fetch and install
+ the package with <TT
+CLASS="LITERAL"
+>pkg_add -r privoxy</TT
+>.</P
+><P
+> The port skeleton and the package can also be downloaded from the
+ <A
+HREF="https://sourceforge.net/project/showfiles.php?group_id=11118"
+TARGET="_top"
+>File Release
+ Page</A
+>, but if you're interested in stable releases only you don't
+ gain anything by using them.</P
+></DIV
+><DIV
+CLASS="SECT3"
+><H3
+CLASS="SECT3"
+><A
NAME="INSTALLATTION-GENTOO"
></A
->2.1.8. Gentoo</H3
+>2.1.9. Gentoo</H3
><P
> Gentoo source packages (Ebuilds) for <SPAN
CLASS="APPLICATION"
>, the
documentation is in <TT
CLASS="FILENAME"
->/usr/share/doc/privoxy-3.0.6</TT
+>/usr/share/doc/privoxy-3.0.7</TT
>
and the Log directory is in <TT
CLASS="FILENAME"
><TD
><PRE
CLASS="SCREEN"
-> tar xzvf privoxy-3.0.6-src* [.tgz or .tar.gz]
- cd privoxy-3.0.6</PRE
+> tar xzvf privoxy-3.0.7-src* [.tgz or .tar.gz]
+ cd privoxy-3.0.7</PRE
></TD
></TR
></TABLE
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.6 User Manual"
+TITLE="Privoxy 3.0.7 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
-TITLE="Privoxy 3.0.6 User Manual"
+TITLE="Privoxy 3.0.7 User Manual"
HREF="index.html"><LINK
REL="NEXT"
TITLE="Installation"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.6 User Manual</TH
+>Privoxy 3.0.7 User Manual</TH
></TR
><TR
><TD
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->, v.3.0.6.</P
+>, v.3.0.7.</P
><DIV
CLASS="SECT2"
><H2
></LI
><LI
><P
-> HTTP/1.1 compliant (but not all optional 1.1 features are supported).
- </P
-></LI
-><LI
-><P
> Support for Perl Compatible Regular Expressions in the configuration files, and
generally a more sophisticated and flexible configuration syntax over
previous versions.
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Privoxy 3.0.6 User Manual</TD
+>Privoxy 3.0.7 User Manual</TD
><TD
WIDTH="34%"
ALIGN="center"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.6 User Manual"
+TITLE="Privoxy 3.0.7 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="What's New in this Release"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.6 User Manual</TH
+>Privoxy 3.0.7 User Manual</TH
></TR
><TR
><TD
> <DIV
CLASS="FIGURE"
><A
-NAME="AEN599"
+NAME="AEN513"
></A
><P
><B
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.6 User Manual"
+TITLE="Privoxy 3.0.7 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Privoxy Copyright, License and History"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.6 User Manual</TH
+>Privoxy 3.0.7 User Manual</TH
></TR
><TR
><TD
HREF="http://www.squid-cache.org/"
TARGET="_top"
>http://www.squid-cache.org/</A
->, a very popular
+>, a popular
caching proxy, which is often used together with <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
><TR
><TD
> <A
+HREF="http://www.pps.jussieu.fr/~jch/software/polipo/"
+TARGET="_top"
+>http://www.pps.jussieu.fr/~jch/software/polipo/</A
+>,
+ <SPAN
+CLASS="APPLICATION"
+>Polipo</SPAN
+> is a caching proxy with advanced features
+ like pipelining, multiplexing and caching of partial instances. In many setups
+ it can be used as <SPAN
+CLASS="APPLICATION"
+>Squid</SPAN
+> replacement.
+ </TD
+></TR
+></TBODY
+></TABLE
+><P
+></P
+>
+ <P
+></P
+><TABLE
+BORDER="0"
+><TBODY
+><TR
+><TD
+> <A
HREF="http://tor.eff.org/"
TARGET="_top"
>http://tor.eff.org/</A
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.6 User Manual"
+TITLE="Privoxy 3.0.7 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Quickstart to Using Privoxy"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.6 User Manual</TH
+>Privoxy 3.0.7 User Manual</TH
></TR
><TR
><TD
> <DIV
CLASS="FIGURE"
><A
-NAME="AEN654"
+NAME="AEN568"
></A
><P
><B
> <DIV
CLASS="FIGURE"
><A
-NAME="AEN698"
+NAME="AEN612"
></A
><P
><B
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.6 User Manual"
+TITLE="Privoxy 3.0.7 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Filter Files"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.6 User Manual</TH
+>Privoxy 3.0.7 User Manual</TH
></TR
><TR
><TD
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.6 User Manual"
+TITLE="Privoxy 3.0.7 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Installation"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.6 User Manual</TH
+>Privoxy 3.0.7 User Manual</TH
></TR
><TR
><TD
><P
> There are many improvements and new features since <SPAN
CLASS="APPLICATION"
->Privoxy 3.0.3</SPAN
+>Privoxy 3.0.6</SPAN
>, the last stable release:</P
><P
> <P
><UL
><LI
><P
-> Multiple <A
-HREF="filter-file.html"
->filter files</A
-> can now be specified in <TT
-CLASS="FILENAME"
->config</TT
->. This allows for
- locally defined filters that can be maintained separately from the filters as
- supplied by the developers, i.e. <TT
-CLASS="FILENAME"
->default.filter</TT
->.
- </P
-></LI
-><LI
-><P
->
- There are a number of new <A
-HREF="actions-file.html"
->actions</A
->:
- </P
-><P
-> <P
-></P
-><UL
-><LI
-><P
-> <TT
-CLASS="LITERAL"
-><A
-HREF="actions-file.html#CONTENT-TYPE-OVERWRITE"
->content-type-overwrite</A
-></TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="LITERAL"
-><A
-HREF="actions-file.html#CRUNCH-CLIENT-HEADER"
->crunch-client-header</A
-></TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="LITERAL"
-><A
-HREF="actions-file.html#CRUNCH-IF-NONE-MATCH"
->crunch-if-none-match</A
-></TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="LITERAL"
-><A
-HREF="actions-file.html#CRUNCH-SERVER-HEADER"
->crunch-server-header</A
-></TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="LITERAL"
-><A
-HREF="actions-file.html#FILTER-CLIENT-HEADERS"
->filter-client-headers</A
-></TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="LITERAL"
-><A
-HREF="actions-file.html#FILTER-SERVER-HEADERS"
->filter-server-headers</A
-></TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="LITERAL"
-><A
-HREF="actions-file.html#FORCE-TEXT-MODE"
->force-text-mode</A
-></TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="LITERAL"
-><A
-HREF="actions-file.html#HANDLE-AS-EMPTY-DOCUMENT"
->handle-as-empty-document</A
-></TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="LITERAL"
-><A
-HREF="actions-file.html#HIDE-ACCEPT-LANGUAGE"
->hide-accept-language</A
-></TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="LITERAL"
-><A
-HREF="actions-file.html#HIDE-CONTENT-DISPOSITION"
->hide-content-disposition</A
-></TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="LITERAL"
-><A
-HREF="actions-file.html#HIDE-IF-MODIFIED-SINCE"
->hide-if-modified-since</A
-></TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="LITERAL"
-><A
-HREF="actions-file.html#INSPECT-JPEGS"
->inspect-jpegs</A
-></TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="LITERAL"
-><A
-HREF="actions-file.html#OVERWRITE-LAST-MODIFIED"
->overwrite-last-modified</A
-></TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="LITERAL"
-><A
-HREF="actions-file.html#REDIRECT"
->redirect</A
-></TT
->
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="LITERAL"
-><A
-HREF="actions-file.html#TREAT-FORBIDDEN-CONNECTS-LIKE-BLOCKS"
->treat-forbidden-connects-like-blocks</A
-></TT
->
- </P
-></LI
-></UL
->
- </P
-><P
-> In addition, <TT
-CLASS="LITERAL"
-><A
-HREF="actions-file.html#FAST-REDIRECTS"
->fast-redirects</A
-></TT
->
- has been significantly improved with enhanced syntax.
- </P
-><P
-> And <TT
-CLASS="LITERAL"
-><A
-HREF="actions-file.html#HIDE-REFERRER"
->hide-referrer</A
-></TT
+> Header filtering can be done with dedicated header filters now. As a result
+ the actions <SPAN
+CLASS="QUOTE"
+>"filter-client-headers"</SPAN
+> and <SPAN
+CLASS="QUOTE"
+>"filter-server-headers"</SPAN
>
- has a new option, <TT
-CLASS="LITERAL"
->conditional block</TT
->.
- </P
-></LI
-><LI
-><P
-> <SPAN
+ that were introduced with <SPAN
CLASS="APPLICATION"
->MS-Windows</SPAN
-> versions can now be
- <A
-HREF="installation.html#INSTALLATION-PACK-WIN"
->installed and
- started as a <SPAN
-CLASS="emphasis"
-><I
-CLASS="EMPHASIS"
->Windows service</I
-></SPAN
-></A
->.
- </P
-></LI
-><LI
-><P
-> <TT
-CLASS="FILENAME"
->config</TT
-> has two new options:
- <A
-HREF="config.html#ENABLE-REMOTE-HTTP-TOGGLE"
->enable-remote-http-toggle</A
->,
- and <A
-HREF="config.html#FORWARDED-CONNECT-RETRIES"
->forwarded-connect-retries</A
->.
- </P
-><P
-> And there is improved handling of the <A
-HREF="config.html#USER-MANUAL"
->user-manual</A
->
- option, for placing documentation and help files on the local system.
- </P
-></LI
-><LI
-><P
-> There are six new <A
-HREF="actions-file.html#FILTER"
->filters</A
->.
- </P
-></LI
-><LI
-><P
-> Actions files problems and suggestions are now being directed to:
- <A
-HREF="http://sourceforge.net/tracker/?group_id=11118&atid=460288"
-TARGET="_top"
->http://sourceforge.net/tracker/?group_id=11118&atid=460288</A
->.
- Please use this to report such configuration related problems as missed
- ads, sites that don't function properly due to one action or another,
- innocent images being blocked, etc.
- </P
-></LI
-><LI
-><P
-> In addition, there are numerous bug fixes and significant enhancements,
- including error pages should no longer be cached if the problem is fixed,
- much better DNS error handling, various logging improvements, and
- configuration updates for better ad blocking and junk elimination.
+>Privoxy 3.0.5</SPAN
+> to apply
+ the content filters to the headers as, well have been removed again.
</P
></LI
></UL
projects / privoxy.git / commitdiff