+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>The Main Configuration File</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
-TITLE="Privoxy 3.1.1 User Manual"
+TITLE="Privoxy 3.0.3 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Privoxy Configuration"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.1.1 User Manual</TH
+>Privoxy 3.0.3 User Manual</TH
></TR
><TR
><TD
><H1
CLASS="SECT1"
><A
-NAME="CONFIG">7. The Main Configuration File</H1
+NAME="CONFIG"
+>7. The Main Configuration File</A
+></H1
><P
> Again, the main configuration file is named <TT
CLASS="FILENAME"
values, all separated by whitespace (any number of spaces or tabs). For
example:</P
><P
-> <TT
+> <VAR
CLASS="LITERAL"
> <P
CLASS="LITERALLAYOUT"
></SPAN
></P
>
- </TT
+ </VAR
> </P
><P
-> Assigns the value <TT
+> Assigns the value <VAR
CLASS="LITERAL"
->/etc/privoxy</TT
+>/etc/privoxy</VAR
> to the option
- <TT
+ <VAR
CLASS="LITERAL"
->confdir</TT
+>confdir</VAR
> and thus indicates that the configuration
directory is named <SPAN
CLASS="QUOTE"
>"/etc/privoxy/"</SPAN
>.</P
><P
-> All options in the config file except for <TT
+> All options in the config file except for <VAR
CLASS="LITERAL"
->confdir</TT
+>confdir</VAR
> and
- <TT
+ <VAR
CLASS="LITERAL"
->logdir</TT
+>logdir</VAR
> are optional. Watch out in the below description
for what happens if you leave them unset.</P
><P
><H2
CLASS="SECT2"
><A
-NAME="CONF-LOG-LOC">7.1. Configuration and Log File Locations</H2
+NAME="CONF-LOG-LOC"
+>7.1. Configuration and Log File Locations</A
+></H2
><P
> <SPAN
CLASS="APPLICATION"
><H4
CLASS="SECT3"
><A
-NAME="CONFDIR">7.1.1. confdir</H4
+NAME="CONFDIR"
+>7.1.1. confdir</A
+></H4
><P
></P
><DIV
><P
> No trailing <SPAN
CLASS="QUOTE"
->"<TT
+>"<VAR
CLASS="LITERAL"
->/</TT
+>/</VAR
>"</SPAN
>, please
</P
><H4
CLASS="SECT3"
><A
-NAME="LOGDIR">7.1.2. logdir</H4
+NAME="LOGDIR"
+>7.1.2. logdir</A
+></H4
><P
></P
><DIV
><P
> No trailing <SPAN
CLASS="QUOTE"
->"<TT
+>"<VAR
CLASS="LITERAL"
->/</TT
+>/</VAR
>"</SPAN
>, please
</P
><H4
CLASS="SECT3"
><A
-NAME="ACTIONSFILE">7.1.3. actionsfile</H4
+NAME="ACTIONSFILE"
+>7.1.3. actionsfile</A
+></H4
><A
NAME="DEFAULT.ACTION"
></A
>Type of value:</DT
><DD
><P
->File name, relative to <TT
+>File name, relative to <VAR
CLASS="LITERAL"
->confdir</TT
->, without the <TT
+>confdir</VAR
+>, without the <VAR
CLASS="LITERAL"
->.action</TT
+>.action</VAR
> suffix</P
></DD
><DT
>Notes:</DT
><DD
><P
-> Multiple <TT
+> Multiple <VAR
CLASS="LITERAL"
->actionsfile</TT
+>actionsfile</VAR
> lines are permitted, and are in fact recommended!
</P
><P
><H4
CLASS="SECT3"
><A
-NAME="FILTERFILE">7.1.4. filterfile</H4
+NAME="FILTERFILE"
+>7.1.4. filterfile</A
+></H4
><A
NAME="DEFAULT.FILTER"
></A
>Type of value:</DT
><DD
><P
->File name, relative to <TT
+>File name, relative to <VAR
CLASS="LITERAL"
->confdir</TT
+>confdir</VAR
></P
></DD
><DT
><DD
><P
> No textual content filtering takes place, i.e. all
- <TT
+ <VAR
CLASS="LITERAL"
>+<A
HREF="actions-file.html#FILTER"
>filter</A
->{<TT
+>{<VAR
CLASS="REPLACEABLE"
-><I
->name</I
-></TT
->}</TT
+>name</VAR
+>}</VAR
>
actions in the actions files are turned neutral.
</P
</P
><P
> The
- <TT
+ <VAR
CLASS="LITERAL"
>+<A
HREF="actions-file.html#FILTER"
>filter</A
->{<TT
+>{<VAR
CLASS="REPLACEABLE"
-><I
->name</I
-></TT
->}</TT
+>name</VAR
+>}</VAR
>
- actions rely on the relevant filter (<TT
+ actions rely on the relevant filter (<VAR
CLASS="REPLACEABLE"
-><I
->name</I
-></TT
+>name</VAR
>)
to be defined in the filter file!
</P
>default.filter</TT
> that contains
a bunch of handy filters for common problems is included in the distribution.
- See the section on the <TT
+ See the section on the <VAR
CLASS="LITERAL"
><A
HREF="actions-file.html#FILTER"
>filter</A
-></TT
+></VAR
>
action for a list.
</P
><H4
CLASS="SECT3"
><A
-NAME="LOGFILE">7.1.5. logfile</H4
+NAME="LOGFILE"
+>7.1.5. logfile</A
+></H4
><P
></P
><DIV
>Type of value:</DT
><DD
><P
->File name, relative to <TT
+>File name, relative to <VAR
CLASS="LITERAL"
->logdir</TT
+>logdir</VAR
></P
></DD
><DT
>Effect if unset:</DT
><DD
><P
-> No log file is used, all log messages go to the console (<TT
+> No log file is used, all log messages go to the console (<VAR
CLASS="LITERAL"
->STDERR</TT
+>STDERR</VAR
>).
</P
></DD
>Notes:</DT
><DD
><P
-> The windows version will additionally log to the console.
- </P
-><P
> The logfile is where all logging and error messages are written. The level
- of detail and number of messages are set with the <TT
+ of detail and number of messages are set with the <VAR
CLASS="LITERAL"
->debug</TT
+>debug</VAR
>
option (see below). The logfile can be useful for tracking down a problem with
<SPAN
><H4
CLASS="SECT3"
><A
-NAME="JARFILE">7.1.6. jarfile</H4
+NAME="JARFILE"
+>7.1.6. jarfile</A
+></H4
><P
></P
><DIV
>Type of value:</DT
><DD
><P
->File name, relative to <TT
+>File name, relative to <VAR
CLASS="LITERAL"
->logdir</TT
+>logdir</VAR
></P
></DD
><DT
><H4
CLASS="SECT3"
><A
-NAME="TRUSTFILE">7.1.7. trustfile</H4
+NAME="TRUSTFILE"
+>7.1.7. trustfile</A
+></H4
><P
></P
><DIV
>Type of value:</DT
><DD
><P
->File name, relative to <TT
+>File name, relative to <VAR
CLASS="LITERAL"
->confdir</TT
+>confdir</VAR
></P
></DD
><DT
>Effect if unset:</DT
><DD
><P
-> The whole trust mechanism is turned off.
+> The entire trust mechanism is turned off.
</P
></DD
><DT
CLASS="APPLICATION"
>Privoxy</SPAN
> will only allow
- access to sites that are named in the trustfile.
- You can also mark sites as trusted referrers (with <TT
-CLASS="LITERAL"
->+</TT
->), with
- the effect that access to untrusted sites will be granted, if a link from a
- trusted referrer was used.
- The link target will then be added to the <SPAN
+ access to sites that are specified in the trustfile. Sites can be listed
+ in one of two ways:
+ </P
+><P
+> Prepending a <VAR
+CLASS="LITERAL"
+>~</VAR
+> character limits access to this site
+ only (and any sub-paths within this site), e.g.
+ <VAR
+CLASS="LITERAL"
+>~www.example.com</VAR
+>.
+ </P
+><P
+> Or, you can designate sites as <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>trusted referrers</I
+></SPAN
+>, by
+ prepending the name with a <VAR
+CLASS="LITERAL"
+>+</VAR
+> character. The effect is that
+ access to untrusted sites will be granted -- but only if a link from this
+ trusted referrer was used. The link target will then be added to the
+ <SPAN
CLASS="QUOTE"
>"trustfile"</SPAN
->.
- Possible applications include limiting Internet access for children.
+> so that future, direct accesses will be granted.
+ Sites added via this mechanism do not become trusted referrers themselves
+ (i.e. they are added with a <VAR
+CLASS="LITERAL"
+>~</VAR
+> designation).
</P
><P
-> If you use <TT
+> If you use the <VAR
CLASS="LITERAL"
->+</TT
-> operator in the trust file, it may grow considerably over time.
+>+</VAR
+> operator in the trust file, it may grow
+ considerably over time.
+ </P
+><P
+> It is recommended that <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> be compiled with
+ the <VAR
+CLASS="LITERAL"
+>--disable-force</VAR
+>, <VAR
+CLASS="LITERAL"
+>--disable-toggle</VAR
+> and
+ <VAR
+CLASS="LITERAL"
+> --disable-editor</VAR
+> options, if this feature is to be
+ used.
+ </P
+><P
+> Possible applications include limiting Internet access for children.
</P
></DD
></DL
><H2
CLASS="SECT2"
><A
-NAME="LOCAL-SET-UP">7.2. Local Set-up Documentation</H2
+NAME="LOCAL-SET-UP"
+>7.2. Local Set-up Documentation</A
+></H2
><P
> If you intend to operate <SPAN
CLASS="APPLICATION"
><H4
CLASS="SECT3"
><A
-NAME="USER-MANUAL">7.2.1. user-manual</H4
+NAME="USER-MANUAL"
+>7.2.1. user-manual</A
+></H4
><P
></P
><DIV
> <A
HREF="http://www.privoxy.org/user-manual/"
TARGET="_top"
->http://www.privoxy.org/<TT
+>http://www.privoxy.org/<VAR
CLASS="REPLACEABLE"
-><I
->version</I
-></TT
+>version</VAR
>/user-manual/</A
>
- will be used, where <TT
+ will be used, where <VAR
CLASS="REPLACEABLE"
-><I
->version</I
-></TT
+>version</VAR
> is the <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
><TD
><PRE
CLASS="SCREEN"
->user-manual file:///usr/share/doc/privoxy-3.1.1/user-manual/</PRE
+> user-manual file:///usr/share/doc/privoxy-3.0.3/user-manual/</PRE
+></TD
+></TR
+></TABLE
+>
+ </P
+><P
+> Windows, in local filesystem, <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>must</I
+></SPAN
+> use forward slash notation:
+ </P
+><P
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="90%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+> user-manual file:/c:/some-dir/privoxy-3.0.3/user-manual/</PRE
+></TD
+></TR
+></TABLE
+>
+ </P
+><P
+> Windows, UNC notation (with forward slashes):
+ </P
+><P
+> <TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="90%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+> user-manual file://///some-server/some-path/privoxy-3.0.3/user-manual/</PRE
></TD
></TR
></TABLE
><TD
><PRE
CLASS="SCREEN"
->user-manual http://local-webserver/privoxy-user-manual/</PRE
+> user-manual http://local-webserver/privoxy-user-manual/</PRE
></TD
></TR
></TABLE
><H4
CLASS="SECT3"
><A
-NAME="TRUST-INFO-URL">7.2.2. trust-info-url</H4
+NAME="TRUST-INFO-URL"
+>7.2.2. trust-info-url</A
+></H4
><P
></P
><DIV
><H4
CLASS="SECT3"
><A
-NAME="ADMIN-ADDRESS">7.2.3. admin-address</H4
+NAME="ADMIN-ADDRESS"
+>7.2.3. admin-address</A
+></H4
><P
></P
><DIV
>Notes:</DT
><DD
><P
-> If both <TT
+> If both <VAR
CLASS="LITERAL"
->admin-address</TT
-> and <TT
+>admin-address</VAR
+> and <VAR
CLASS="LITERAL"
->proxy-info-url</TT
+>proxy-info-url</VAR
>
are unset, the whole "Local Privoxy Support" box on all generated pages will
not be shown.
><H4
CLASS="SECT3"
><A
-NAME="PROXY-INFO-URL">7.2.4. proxy-info-url</H4
+NAME="PROXY-INFO-URL"
+>7.2.4. proxy-info-url</A
+></H4
><P
></P
><DIV
>Notes:</DT
><DD
><P
-> If both <TT
+> If both <VAR
CLASS="LITERAL"
->admin-address</TT
-> and <TT
+>admin-address</VAR
+> and <VAR
CLASS="LITERAL"
->proxy-info-url</TT
+>proxy-info-url</VAR
>
are unset, the whole "Local Privoxy Support" box on all generated pages will
not be shown.
><H2
CLASS="SECT2"
><A
-NAME="DEBUGGING">7.3. Debugging</H2
+NAME="DEBUGGING"
+>7.3. Debugging</A
+></H2
><P
> These options are mainly useful when tracing a problem.
Note that you might also want to invoke
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> with the <TT
+> with the <VAR
CLASS="LITERAL"
->--no-daemon</TT
+>--no-daemon</VAR
>
command line option when debugging.
</P
><H4
CLASS="SECT3"
><A
-NAME="DEBUG">7.3.1. debug</H4
+NAME="DEBUG"
+>7.3.1. debug</A
+></H4
><P
></P
><DIV
</P
><P
> To select multiple debug levels, you can either add them or use
- multiple <TT
+ multiple <VAR
CLASS="LITERAL"
->debug</TT
+>debug</VAR
> lines.
</P
><P
><H4
CLASS="SECT3"
><A
-NAME="SINGLE-THREADED">7.3.2. single-threaded</H4
+NAME="SINGLE-THREADED"
+>7.3.2. single-threaded</A
+></H4
><P
></P
><DIV
><H2
CLASS="SECT2"
><A
-NAME="ACCESS-CONTROL">7.4. Access Control and Security</H2
+NAME="ACCESS-CONTROL"
+>7.4. Access Control and Security</A
+></H2
><P
> This section of the config file controls the security-relevant aspects
of <SPAN
><H4
CLASS="SECT3"
><A
-NAME="LISTEN-ADDRESS">7.4.1. listen-address</H4
+NAME="LISTEN-ADDRESS"
+>7.4.1. listen-address</A
+></H4
><P
></P
><DIV
>Type of value:</DT
><DD
><P
->[<TT
+>[<VAR
CLASS="REPLACEABLE"
-><I
->IP-Address</I
-></TT
->]:<TT
+>IP-Address</VAR
+>]:<VAR
CLASS="REPLACEABLE"
-><I
->Port</I
-></TT
+>Port</VAR
></P
></DD
><DT
CLASS="APPLICATION"
>Privoxy</SPAN
> to untrusted users, you will
- also want to turn off the <TT
+ also want to turn off the <VAR
CLASS="LITERAL"
><A
HREF="config.html#ENABLE-EDIT-ACTIONS"
>enable-edit-actions</A
-></TT
+></VAR
> and
- <TT
+ <VAR
CLASS="LITERAL"
><A
HREF="config.html#ENABLE-REMOTE-TOGGLE"
>enable-remote-toggle</A
-></TT
+></VAR
>
options!
</P
><H4
CLASS="SECT3"
><A
-NAME="TOGGLE">7.4.2. toggle</H4
+NAME="TOGGLE"
+>7.4.2. toggle</A
+></H4
><P
></P
><DIV
>"toggled off"</SPAN
> mode, i.e. behave like a normal, content-neutral
proxy where all ad blocking, filtering, etc are disabled. See
- <TT
+ <VAR
CLASS="LITERAL"
->enable-remote-toggle</TT
+>enable-remote-toggle</VAR
> below. This is not really useful
anymore, since toggling is much easier via <A
HREF="http://config.privoxy.org/toggle"
><H4
CLASS="SECT3"
><A
-NAME="ENABLE-REMOTE-TOGGLE">7.4.3. enable-remote-toggle</H4
+NAME="ENABLE-REMOTE-TOGGLE"
+>7.4.3. enable-remote-toggle</A
+></H4
><P
></P
><DIV
<SPAN
CLASS="QUOTE"
>"ACLs"</SPAN
-> and <TT
+> and <VAR
CLASS="LITERAL"
->listen-address</TT
+>listen-address</VAR
> above) can
toggle it for all users. So this option is <SPAN
CLASS="emphasis"
><H4
CLASS="SECT3"
><A
-NAME="ENABLE-EDIT-ACTIONS">7.4.4. enable-edit-actions</H4
+NAME="ENABLE-EDIT-ACTIONS"
+>7.4.4. enable-edit-actions</A
+></H4
><P
></P
><DIV
<SPAN
CLASS="QUOTE"
>"ACLs"</SPAN
-> and <TT
+> and <VAR
CLASS="LITERAL"
->listen-address</TT
+>listen-address</VAR
> above) can
modify its configuration for all users. So this option is <SPAN
CLASS="emphasis"
><H4
CLASS="SECT3"
><A
-NAME="ACLS">7.4.5. ACLs: permit-access and deny-access</H4
+NAME="ACLS"
+>7.4.5. ACLs: permit-access and deny-access</A
+></H4
><A
NAME="PERMIT-ACCESS"
></A
>Type of value:</DT
><DD
><P
-> <TT
+> <VAR
CLASS="REPLACEABLE"
-><I
->src_addr</I
-></TT
->[/<TT
+>src_addr</VAR
+>[/<VAR
CLASS="REPLACEABLE"
-><I
->src_masklen</I
-></TT
+>src_masklen</VAR
>]
- [<TT
+ [<VAR
CLASS="REPLACEABLE"
-><I
->dst_addr</I
-></TT
->[/<TT
+>dst_addr</VAR
+>[/<VAR
CLASS="REPLACEABLE"
-><I
->dst_masklen</I
-></TT
+>dst_masklen</VAR
>]]
</P
><P
-> Where <TT
+> Where <VAR
CLASS="REPLACEABLE"
-><I
->src_addr</I
-></TT
+>src_addr</VAR
> and
- <TT
+ <VAR
CLASS="REPLACEABLE"
-><I
->dst_addr</I
-></TT
+>dst_addr</VAR
> are IP addresses in dotted decimal notation or valid
- DNS names, and <TT
+ DNS names, and <VAR
CLASS="REPLACEABLE"
-><I
->src_masklen</I
-></TT
+>src_masklen</VAR
> and
- <TT
+ <VAR
CLASS="REPLACEABLE"
-><I
->dst_masklen</I
-></TT
+>dst_masklen</VAR
> are subnet masks in CIDR notation, i.e. integer
values from 2 to 30 representing the length (in bits) of the network address. The masks and the whole
destination part are optional.
>Effect if unset:</DT
><DD
><P
-> Don't restrict access further than implied by <TT
+> Don't restrict access further than implied by <VAR
CLASS="LITERAL"
->listen-address</TT
+>listen-address</VAR
>
</P
></DD
CLASS="APPLICATION"
>Privoxy</SPAN
>
- talks only to IP addresses that match at least one <TT
+ talks only to IP addresses that match at least one <VAR
CLASS="LITERAL"
->permit-access</TT
+>permit-access</VAR
> line
- and don't match any subsequent <TT
+ and don't match any subsequent <VAR
CLASS="LITERAL"
->deny-access</TT
+>deny-access</VAR
> line. In other words, the
- last match wins, with the default being <TT
+ last match wins, with the default being <VAR
CLASS="LITERAL"
->deny-access</TT
+>deny-access</VAR
>.
</P
><P
> If <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> is using a forwarder (see <TT
+> is using a forwarder (see <VAR
CLASS="LITERAL"
->forward</TT
+>forward</VAR
> below)
- for a particular destination URL, the <TT
+ for a particular destination URL, the <VAR
CLASS="REPLACEABLE"
-><I
->dst_addr</I
-></TT
+>dst_addr</VAR
>
that is examined is the address of the forwarder and <SPAN
CLASS="emphasis"
><DD
><P
> Explicitly define the default behavior if no ACL and
- <TT
+ <VAR
CLASS="LITERAL"
->listen-address</TT
+>listen-address</VAR
> are set: <SPAN
CLASS="QUOTE"
>"localhost"</SPAN
>
- is OK. The absence of a <TT
+ is OK. The absence of a <VAR
CLASS="REPLACEABLE"
-><I
->dst_addr</I
-></TT
+>dst_addr</VAR
> implies that
<SPAN
CLASS="emphasis"
><H4
CLASS="SECT3"
><A
-NAME="BUFFER-LIMIT">7.4.6. buffer-limit</H4
+NAME="BUFFER-LIMIT"
+>7.4.6. buffer-limit</A
+></H4
><P
></P
><DIV
>Notes:</DT
><DD
><P
-> For content filtering, i.e. the <TT
+> For content filtering, i.e. the <VAR
CLASS="LITERAL"
->+filter</TT
+>+filter</VAR
> and
- <TT
+ <VAR
CLASS="LITERAL"
->+deanimate-gif</TT
+>+deanimate-gif</VAR
> actions, it is necessary that
<SPAN
CLASS="APPLICATION"
Hence this option.
</P
><P
-> When a document buffer size reaches the <TT
+> When a document buffer size reaches the <VAR
CLASS="LITERAL"
->buffer-limit</TT
+>buffer-limit</VAR
>, it is
flushed to the client unfiltered and no further attempt to
filter the rest of the document is made. Remember that there may be multiple threads
- running, which might require up to <TT
+ running, which might require up to <VAR
CLASS="LITERAL"
->buffer-limit</TT
+>buffer-limit</VAR
> Kbytes
<SPAN
CLASS="emphasis"
><H2
CLASS="SECT2"
><A
-NAME="FORWARDING">7.5. Forwarding</H2
+NAME="FORWARDING"
+>7.5. Forwarding</A
+></H2
><P
> This feature allows routing of HTTP requests through a chain of
multiple proxies.
><H4
CLASS="SECT3"
><A
-NAME="FORWARD">7.5.1. forward</H4
+NAME="FORWARD"
+>7.5.1. forward</A
+></H4
><P
></P
><DIV
>Type of value:</DT
><DD
><P
-> <TT
+> <VAR
CLASS="REPLACEABLE"
-><I
->target_pattern</I
-></TT
+>target_pattern</VAR
>
- <TT
+ <VAR
CLASS="REPLACEABLE"
-><I
->http_parent</I
-></TT
->[:<TT
+>http_parent</VAR
+>[:<VAR
CLASS="REPLACEABLE"
-><I
->port</I
-></TT
+>port</VAR
>]
</P
><P
-> where <TT
+> where <VAR
CLASS="REPLACEABLE"
-><I
->target_pattern</I
-></TT
+>target_pattern</VAR
> is a <A
HREF="actions-file.html#AF-PATTERNS"
>URL pattern</A
>
- that specifies to which requests (i.e. URLs) this forward rule shall apply. Use <TT
+ that specifies to which requests (i.e. URLs) this forward rule shall apply. Use <VAR
CLASS="LITERAL"
->/</TT
+>/</VAR
> to
denote <SPAN
CLASS="QUOTE"
>"all URLs"</SPAN
>.
- <TT
+ <VAR
CLASS="REPLACEABLE"
-><I
->http_parent</I
-></TT
->[:<TT
+>http_parent</VAR
+>[:<VAR
CLASS="REPLACEABLE"
-><I
->port</I
-></TT
+>port</VAR
>]
is the DNS name or IP address of the parent HTTP proxy through which the requests should be forwarded,
optionally followed by its listening port (default: 8080).
- Use a single dot (<TT
+ Use a single dot (<VAR
CLASS="LITERAL"
->.</TT
+>.</VAR
>) to denote <SPAN
CLASS="QUOTE"
>"no forwarding"</SPAN
>Notes:</DT
><DD
><P
-> If <TT
+> If <VAR
CLASS="REPLACEABLE"
-><I
->http_parent</I
-></TT
+>http_parent</VAR
> is <SPAN
CLASS="QUOTE"
>"."</SPAN
><H4
CLASS="SECT3"
><A
-NAME="SOCKS">7.5.2. forward-socks4 and forward-socks4a</H4
+NAME="SOCKS"
+>7.5.2. forward-socks4 and forward-socks4a</A
+></H4
><A
NAME="FORWARD-SOCKS4"
></A
>Type of value:</DT
><DD
><P
-> <TT
+> <VAR
CLASS="REPLACEABLE"
-><I
->target_pattern</I
-></TT
+>target_pattern</VAR
>
- <TT
+ <VAR
CLASS="REPLACEABLE"
-><I
->socks_proxy</I
-></TT
->[:<TT
+>socks_proxy</VAR
+>[:<VAR
CLASS="REPLACEABLE"
-><I
->port</I
-></TT
+>port</VAR
>]
- <TT
+ <VAR
CLASS="REPLACEABLE"
-><I
->http_parent</I
-></TT
->[:<TT
+>http_parent</VAR
+>[:<VAR
CLASS="REPLACEABLE"
-><I
->port</I
-></TT
+>port</VAR
>]
</P
><P
-> where <TT
+> where <VAR
CLASS="REPLACEABLE"
-><I
->target_pattern</I
-></TT
+>target_pattern</VAR
> is a <A
HREF="actions-file.html#AF-PATTERNS"
>URL pattern</A
>
- that specifies to which requests (i.e. URLs) this forward rule shall apply. Use <TT
+ that specifies to which requests (i.e. URLs) this forward rule shall apply. Use <VAR
CLASS="LITERAL"
->/</TT
+>/</VAR
> to
denote <SPAN
CLASS="QUOTE"
>"all URLs"</SPAN
>.
- <TT
+ <VAR
CLASS="REPLACEABLE"
-><I
->http_parent</I
-></TT
-> and <TT
+>http_parent</VAR
+> and <VAR
CLASS="REPLACEABLE"
-><I
->socks_proxy</I
-></TT
+>socks_proxy</VAR
>
- are IP addresses in dotted decimal notation or valid DNS names (<TT
+ are IP addresses in dotted decimal notation or valid DNS names (<VAR
CLASS="REPLACEABLE"
-><I
->http_parent</I
-></TT
+>http_parent</VAR
>
may be <SPAN
CLASS="QUOTE"
CLASS="QUOTE"
>"no HTTP forwarding"</SPAN
>), and the optional
- <TT
+ <VAR
CLASS="REPLACEABLE"
-><I
->port</I
-></TT
+>port</VAR
> parameters are TCP ports, i.e. integer values from 1 to 64535
</P
></DD
> Multiple lines are OK, they are checked in sequence, and the last match wins.
</P
><P
-> The difference between <TT
+> The difference between <VAR
CLASS="LITERAL"
->forward-socks4</TT
-> and <TT
+>forward-socks4</VAR
+> and <VAR
CLASS="LITERAL"
->forward-socks4a</TT
+>forward-socks4a</VAR
>
is that in the SOCKS 4A protocol, the DNS resolution of the target hostname happens on the SOCKS
server, while in SOCKS 4 it happens locally.
</P
><P
-> If <TT
+> If <VAR
CLASS="REPLACEABLE"
-><I
->http_parent</I
-></TT
+>http_parent</VAR
> is <SPAN
CLASS="QUOTE"
>"."</SPAN
><H4
CLASS="SECT3"
><A
-NAME="ADVANCED-FORWARDING-EXAMPLES">7.5.3. Advanced Forwarding Examples</H4
+NAME="ADVANCED-FORWARDING-EXAMPLES"
+>7.5.3. Advanced Forwarding Examples</A
+></H4
><P
> If you have links to multiple ISPs that provide various special content
only to their subscribers, you can configure multiple <SPAN
CLASS="APPLICATION"
>squid</SPAN
> locally, then chain as
- <TT
+ <VAR
CLASS="LITERAL"
->browser -> squid -> privoxy</TT
+>browser -> squid -> privoxy</VAR
> is the recommended way. </P
><P
> Assuming that <SPAN
CLASS="APPLICATION"
>squid</SPAN
>'s address and port.
- Squid normally uses port 3128. If unsure consult <TT
+ Squid normally uses port 3128. If unsure consult <VAR
CLASS="LITERAL"
->http_port</TT
+>http_port</VAR
> in <TT
CLASS="FILENAME"
>squid.conf</TT
>.</P
><P
> You could just as well decide to only forward requests for Windows executables through
- a virus-scanning parent proxy, say, on <TT
+ a virus-scanning parent proxy, say, on <VAR
CLASS="LITERAL"
->antivir.example.com</TT
+>antivir.example.com</VAR
>, port 8010:</P
><P
> <TABLE
><H2
CLASS="SECT2"
><A
-NAME="WINDOWS-GUI">7.6. Windows GUI Options</H2
+NAME="WINDOWS-GUI"
+>7.6. Windows GUI Options</A
+></H2
><P
> <SPAN
CLASS="APPLICATION"
>"Privoxy"</SPAN
> is active. To turn off, set to 0.</P
><P
-> <TT
+> <VAR
CLASS="LITERAL"
> <P
CLASS="LITERALLAYOUT"
><br>
</P
>
- </TT
+ </VAR
></P
><A
NAME="LOG-MESSAGES"
> will log messages to the console
window:</P
><P
-> <TT
+> <VAR
CLASS="LITERAL"
> <P
CLASS="LITERALLAYOUT"
><br>
</P
>
- </TT
+ </VAR
></P
><A
NAME="LOG-BUFFER-SIZE"
> Warning: Setting this to 0 will result in the buffer to grow infinitely and
eat up all your memory!</P
><P
-> <TT
+> <VAR
CLASS="LITERAL"
> <P
CLASS="LITERALLAYOUT"
><br>
</P
>
- </TT
+ </VAR
></P
><A
NAME="LOG-MAX-LINES"
> is the maximum number of lines held
in the log buffer. See above.</P
><P
-> <TT
+> <VAR
CLASS="LITERAL"
> <P
CLASS="LITERALLAYOUT"
><br>
</P
>
- </TT
+ </VAR
></P
><A
NAME="LOG-HIGHLIGHT-MESSAGES"
> will highlight portions of the log
messages with a bold-faced font:</P
><P
-> <TT
+> <VAR
CLASS="LITERAL"
> <P
CLASS="LITERALLAYOUT"
><br>
</P
>
- </TT
+ </VAR
></P
><A
NAME="LOG-FONT-NAME"
><P
> The font used in the console window:</P
><P
-> <TT
+> <VAR
CLASS="LITERAL"
> <P
CLASS="LITERALLAYOUT"
><br>
</P
>
- </TT
+ </VAR
></P
><A
NAME="LOG-FONT-SIZE"
><P
> Font size used in the console window:</P
><P
-> <TT
+> <VAR
CLASS="LITERAL"
> <P
CLASS="LITERALLAYOUT"
><br>
</P
>
- </TT
+ </VAR
></P
><A
NAME="SHOW-ON-TASK-BAR"
> will appear as a button on the Task bar
when minimized:</P
><P
-> <TT
+> <VAR
CLASS="LITERAL"
> <P
CLASS="LITERALLAYOUT"
><br>
</P
>
- </TT
+ </VAR
></P
><A
NAME="CLOSE-BUTTON-MINIMIZES"
> instead of closing
the program (close with the exit option on the File menu).</P
><P
-> <TT
+> <VAR
CLASS="LITERAL"
> <P
CLASS="LITERALLAYOUT"
><br>
</P
>
- </TT
+ </VAR
></P
><A
NAME="HIDE-CONSOLE"
> will disconnect from and hide the
command console.</P
><P
-> <TT
+> <VAR
CLASS="LITERAL"
> <P
CLASS="LITERALLAYOUT"
><br>
</P
>
- </TT
+ </VAR
></P
></DIV
></DIV
projects / privoxy.git / blobdiff