-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-<HTML
-><HEAD
-><TITLE
->What's New in this Release</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-REL="HOME"
-TITLE="Privoxy 3.0.11 User Manual"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="Installation"
-HREF="installation.html"><LINK
-REL="NEXT"
-TITLE="Quickstart to Using Privoxy"
-HREF="quickstart.html"><LINK
-REL="STYLESHEET"
-TYPE="text/css"
-HREF="../p_doc.css"><META
-HTTP-EQUIV="Content-Type"
-CONTENT="text/html;
-charset=ISO-8859-1">
-<LINK REL="STYLESHEET" TYPE="text/css" HREF="p_doc.css">
-</head
-><BODY
-CLASS="SECT1"
-BGCOLOR="#EEEEEE"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->Privoxy 3.0.11 User Manual</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="installation.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="quickstart.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="WHATSNEW"
->3. What's New in this Release</A
-></H1
-><P
-> There are only a few improvements and new features since
- <SPAN
-CLASS="APPLICATION"
->Privoxy 3.0.10</SPAN
->, the last stable release:</P
-><P
-> <P
-></P
-><UL
-><LI
-><P
-> On most platforms, outgoing connections can be kept alive and
- reused if the server supports it. Whether or not this improves
- things depends on the connection.
- </P
-></LI
-><LI
-><P
-> When dropping privileges, membership in supplementary groups
- is given up as well. Not doing that can lead to Privoxy running
- with more rights than necessary and violates the principle of
- least privilege. Users of the --user option are advised to update.
- Thanks to Matthias Drochner for reporting the problem,
- providing the initial patch and testing the final version.
- </P
-></LI
-><LI
-><P
-> Passing invalid users or groups with the --user option
- didn't lead to program exit. Regression introduced in 3.0.7.
- </P
-></LI
-><LI
-><P
-> The match all section has been moved from default.action
- to a new file called match-all.action. As a result the
- default.action no longer needs to be touched by the user
- and can be safely overwritten by updates.
- </P
-></LI
-><LI
-><P
-> The standard.action file has been removed. Its content
- is now part of the default.action file.
- </P
-></LI
-><LI
-><P
-> In some situations the logged content length was slightly too low.
- </P
-></LI
-><LI
-><P
-> Crunched requests are logged with their own log level.
- If you used "debug 1" in the past, you'll probably want
- to additionally enable "debug 1024", otherwise only passed
- requests will be logged. If you only care about crunched
- requests, simply replace "debug 1" with "debug 1024".
- </P
-></LI
-><LI
-><P
-> The crunch reason has been moved to the beginning of the
- crunch message. For HTTP URLs, the protocol is logged as well.
- </P
-></LI
-><LI
-><P
-> Log messages are shortened by not printing the thread id
- on its own (as opposed to putting it inside "Privoxy()".
- </P
-></LI
-><LI
-><P
-> The config option socket-timeout has been added to control
- the time Privoxy waits for data to arrive on a socket.
- </P
-></LI
-><LI
-><P
-> Support for remote toggling is controlled by the configure
- option --disable-toggle only. In previous versions it also
- depended on the action editor and thus configuring with the
- --disable-editor option would disable remote toggling support
- as well.
- </P
-></LI
-><LI
-><P
-> Requests with invalid HTTP versions are rejected.
- </P
-></LI
-><LI
-><P
-> The template symbol @date@ can be used to include a date(1)-like
- time string. Initial patch submitted by Endre Szabo.
- </P
-></LI
-><LI
-><P
-> Responses from shoutcast servers are accepted again.
- Problem reported and fix suggested by Stefan.
- </P
-></LI
-><LI
-><P
-> The hide-forwarded-for-headers action has been replaced with
- the change-x-forwarded-for{} action which can also be used to
- add X-Forwarded-For headers. The latter functionality already
- existed in Privoxy versions prior to 3.0.7 but has been removed
- as it was often used unintentionally (by not using the
- hide-forwarded-for-headers action).
- </P
-></LI
-><LI
-><P
-> A "clear log" view option was added to the mingw32 version
- to clear out all of the lines in the Privoxy log window.
- Based on a patch submitted by T Ford.
- </P
-></LI
-><LI
-><P
-> The mingw32 version uses "critical sections" now, which prevents
- log message corruption under load. As a side effect, the
- "no thread-safe PRNG" warning could be removed as well.
- </P
-></LI
-><LI
-><P
-> The mingw32 version's task bar icon is crossed out and
- the color changed to gray if Privoxy is toggled off.
- </P
-></LI
-></UL
-></P
-><P
-> For a more detailed list of changes please have a look at the ChangeLog.</P
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="UPGRADERSNOTE"
->3.1. Note to Upgraders</A
-></H2
-><P
-> A quick list of things to be aware of before upgrading from earlier
- versions of <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
->:</P
-><P
-> <P
-></P
-><UL
-><LI
-><P
-> The recommended way to upgrade <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> is to backup your old
- configuration files, install the new ones, verify that <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
->
- is working correctly and finally merge back your changes using
- <SPAN
-CLASS="APPLICATION"
->diff</SPAN
-> and maybe <SPAN
-CLASS="APPLICATION"
->patch</SPAN
->.
- </P
-><P
-> There are a number of new features in each <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> release and
- most of them have to be explicitly enabled in the configuration
- files. Old configuration files obviously don't do that and due
- to syntax changes using old configuration files with a new
- <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> isn't always possible anyway.
- </P
-></LI
-><LI
-><P
->
- Note that some installers remove earlier versions completely,
- including configuration files, therefore you should really save
- any important configuration files!
- </P
-></LI
-><LI
-><P
->
- On the other hand, other installers don't overwrite existing configuration
- files, thinking you will want to do that yourself.
- </P
-></LI
-><LI
-><P
->
- <TT
-CLASS="FILENAME"
->standard.action</TT
-> has been merged into
- the <TT
-CLASS="FILENAME"
->default.action</TT
-> file.
- </P
-></LI
-><LI
-><P
-> In the default configuration only fatal errors are logged now.
- You can change that in the <A
-HREF="config.html#DEBUG"
->debug section</A
->
- of the configuration file. You may also want to enable more verbose
- logging until you verified that the new <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> version is working
- as expected.
- </P
-></LI
-><LI
-><P
-> Three other config file settings are now off by default:
- <A
-HREF="config.html#ENABLE-REMOTE-TOGGLE"
->enable-remote-toggle</A
->,
- <A
-HREF="config.html#ENABLE-REMOTE-HTTP-TOGGLE"
->enable-remote-http-toggle</A
->,
- and <A
-HREF="config.html#ENABLE-EDIT-ACTIONS"
->enable-edit-actions</A
->.
- If you use or want these, you will need to explicitly enable them, and
- be aware of the security issues involved.
- </P
-></LI
-></UL
-></P
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="installation.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="quickstart.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Installation</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Quickstart to Using Privoxy</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+
+<html>
+<head>
+ <title>What's New in this Release</title>
+ <meta name="GENERATOR" content=
+ "Modular DocBook HTML Stylesheet Version 1.79">
+ <link rel="HOME" title="Privoxy 3.0.22 User Manual" href="index.html">
+ <link rel="PREVIOUS" title="Installation" href="installation.html">
+ <link rel="NEXT" title="Quickstart to Using Privoxy" href=
+ "quickstart.html">
+ <link rel="STYLESHEET" type="text/css" href="../p_doc.css">
+ <meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <link rel="STYLESHEET" type="text/css" href="p_doc.css">
+</head>
+
+<body class="SECT1" bgcolor="#EEEEEE" text="#000000" link="#0000FF" vlink=
+"#840084" alink="#0000FF">
+ <div class="NAVHEADER">
+ <table summary="Header navigation table" width="100%" border="0"
+ cellpadding="0" cellspacing="0">
+ <tr>
+ <th colspan="3" align="center">Privoxy 3.0.22 User Manual</th>
+ </tr>
+
+ <tr>
+ <td width="10%" align="left" valign="bottom"><a href=
+ "installation.html" accesskey="P">Prev</a></td>
+
+ <td width="80%" align="center" valign="bottom"></td>
+
+ <td width="10%" align="right" valign="bottom"><a href=
+ "quickstart.html" accesskey="N">Next</a></td>
+ </tr>
+ </table>
+ <hr align="left" width="100%">
+ </div>
+
+ <div class="SECT1">
+ <h1 class="SECT1"><a name="WHATSNEW" id="WHATSNEW">3. What's New in this
+ Release</a></h1>
+
+ <p><span class="APPLICATION">Privoxy 3.0.22</span> stable is mainly a
+ bug-fix release, it also has a couple of new features, though. Note that
+ the first two entries in the ChangeLog below refer to security
+ issues:</p>
+
+ <ul>
+ <li>
+ <p>Bug fixes:</p>
+
+ <ul>
+ <li>
+ <p>Fixed a memory leak when rejecting client connections due to
+ the socket limit being reached (CID 66382). This affected Privoxy
+ 3.0.21 when compiled with IPv6 support (on most platforms this is
+ the default).</p>
+ </li>
+
+ <li>
+ <p>Fixed an immediate-use-after-free bug (CID 66394) and two
+ additional unconfirmed use-after-free complaints made by Coverity
+ scan (CID 66391, CID 66376).</p>
+ </li>
+
+ <li>
+ <p>Actually show the FORCE_PREFIX value on the show-status
+ page.</p>
+ </li>
+
+ <li>
+ <p>Properly deal with Keep-Alive headers with timeout= parameters
+ If the timeout still can't be parsed, use the configured timeout
+ instead of preventing the client from keeping the connection
+ alive. Fixes #3615312/#870 reported by Bernard Guillot.</p>
+ </li>
+
+ <li>
+ <p>Not using any filter files no longer results in warning
+ messages unless an action file is referencing header taggers or
+ filters. Reported by Stefan Kurtz in #3614835.</p>
+ </li>
+
+ <li>
+ <p>Fixed a bug that prevented Privoxy from reusing some reusable
+ connections. Two bit masks with different purpose unintentionally
+ shared the same bit.</p>
+ </li>
+
+ <li>
+ <p>A couple of additional bugs were discovered by Coverity Scan.
+ The fixes that are not expected to affect users are not
+ explicitly mentioned here, for details please have a look at the
+ CVS logs.</p>
+ </li>
+ </ul>
+ </li>
+
+ <li>
+ <p>General improvements:</p>
+
+ <ul>
+ <li>
+ <p>Introduced negative tag patterns NO-REQUEST-TAG and
+ NO-RESPONSE-TAG. They apply if no matching tag is found after
+ parsing client or server headers.</p>
+ </li>
+
+ <li>
+ <p>Add support for external filters which allow to process the
+ response body with a script or program written in any language
+ the platform supports. External filters are enabled with
+ +external-filter{} after they have been defined in one of the
+ filter files with a header line starting with "EXTERNAL-FILTER:".
+ External filter support is experimental, not compiled by default
+ and known not to work on all platforms.</p>
+ </li>
+
+ <li>
+ <p>Add support for the 'PATCH' method as defined in RFC5789.</p>
+ </li>
+
+ <li>
+ <p>Reject requests with unsupported Expect header values. Fixes a
+ couple of Co-Advisor tests.</p>
+ </li>
+
+ <li>
+ <p>Normalize the HTTP-version in forwarded requests and
+ responses. This is an explicit RFC 2616 MUST and RFC 7230
+ mandates that intermediaries send their own HTTP-version in
+ forwarded messages.</p>
+ </li>
+
+ <li>
+ <p>Client 'Keep-Alive' headers are no longer forwarded. From a
+ user's point of view it doesn't really matter, but RFC 2616
+ (obsolete) mandates that the header is removed and this fixes a
+ Co-Advisor complaint.</p>
+ </li>
+
+ <li>
+ <p>Change declared template file encoding to UTF-8. The templates
+ already used a subset of UTF-8 anyway and changing the
+ declaration allows to properly display UTF-8 characters used in
+ the action files. This change may require existing action files
+ with ISO-8859-1 characters that aren't valid UTF-8 to be
+ converted to UTF-8. Requested by Sam Chen in #582.</p>
+ </li>
+
+ <li>
+ <p>Do not pass rejected keep-alive timeouts to the server. It
+ might not have caused any problems (we know of), but doing the
+ right thing shouldn't hurt either.</p>
+ </li>
+
+ <li>
+ <p>Let log_error() use its own buffer size #define to make
+ changing the log buffer size slightly less inconvenient.</p>
+ </li>
+
+ <li>
+ <p>Turned single-threaded into a "proper" toggle directive with
+ arguments.</p>
+ </li>
+
+ <li>
+ <p>CGI templates no longer enforce new windows for some
+ links.</p>
+ </li>
+
+ <li>
+ <p>Remove an undocumented workaround ('HOST' header removal) for
+ an Apple iTunes bug that according to #729900 got fixed in
+ 2003.</p>
+ </li>
+ </ul>
+ </li>
+
+ <li>
+ <p>Action file improvements:</p>
+
+ <ul>
+ <li>
+ <p>The pattern 'promotions.' is no longer being blocked. Reported
+ by rakista in #3608540.</p>
+ </li>
+
+ <li>
+ <p>Disable fast-redirects for .microsofttranslator.com/.</p>
+ </li>
+
+ <li>
+ <p>Disable filter{banners-by-size} for
+ .dgb-tagungszentren.de/.</p>
+ </li>
+
+ <li>
+ <p>Add adn.speedtest.net as a site-specific unblocker. Support
+ request #3612908.</p>
+ </li>
+
+ <li>
+ <p>Disable filter{banners-by-size} for creativecommons.org/.</p>
+ </li>
+
+ <li>
+ <p>Block requests to data.gosquared.com/. Reported by cbug in
+ #3613653.</p>
+ </li>
+
+ <li>
+ <p>Unblock .conrad./newsletter/. Reported by David Bo in
+ #3614238.</p>
+ </li>
+
+ <li>
+ <p>Unblock .bundestag.de/.</p>
+ </li>
+
+ <li>
+ <p>Unblock .rote-hilfe.de/.</p>
+ </li>
+
+ <li>
+ <p>Disable fast-redirects for .facebook.com/plugins/like.php.</p>
+ </li>
+
+ <li>
+ <p>Unblock Stackexchange popup URLs that aren't used to serve
+ ads. Reported by David Wagner in #3615179.</p>
+ </li>
+
+ <li>
+ <p>Disable fast-redirects for creativecommons.org/.</p>
+ </li>
+
+ <li>
+ <p>Unblock .stopwatchingus.info/.</p>
+ </li>
+
+ <li>
+ <p>Block requests for .adcash.com/script/. Reported by
+ Tyrexionibus in #3615289.</p>
+ </li>
+
+ <li>
+ <p>Disable HTML filters if the response was tagged as JavaScript.
+ Filtering JavaScript code with filters intended to deal with HTML
+ is usually a waste of time and, more importantly, may break
+ stuff.</p>
+ </li>
+
+ <li>
+ <p>Use a custom redirect{} for
+ .washingtonpost.com/wp-apps/imrs\.php\?src= Previously enabling
+ the 'Advanced' settings (or manually enabling +fast-redirects{})
+ prevented some images from being loaded properly.</p>
+ </li>
+
+ <li>
+ <p>Unblock "adina*." Fixes #919 reported by Morton A.
+ Goldberg.</p>
+ </li>
+
+ <li>
+ <p>Block '/.*DigiAd'.</p>
+ </li>
+
+ <li>
+ <p>Unblock 'adele*.'. Reported by Adele Lime in #1663.</p>
+ </li>
+
+ <li>
+ <p>Disable banners-by-size for kggp.de/.</p>
+ </li>
+ </ul>
+ </li>
+
+ <li>
+ <p>Filter file improvements & bug fixes:</p>
+
+ <ul>
+ <li>
+ <p>Decrease the chances that js-annoyances creates invalid
+ JavaScript. Submitted by John McGowan on ijbswa-users@.</p>
+ </li>
+
+ <li>
+ <p>Let the msn filter hide 'related' ads again.</p>
+ </li>
+
+ <li>
+ <p>Remove a stray '1' in the 'html-annoyances' filter.</p>
+ </li>
+
+ <li>
+ <p>Prevent img-reorder from messing up img tags with empty src
+ attributes. Fixes #880 reported by Duncan.</p>
+ </li>
+ </ul>
+ </li>
+
+ <li>
+ <p>Documentation improvements:</p>
+
+ <ul>
+ <li>
+ <p>Updated the 'Would you like to donate?' section.</p>
+ </li>
+
+ <li>
+ <p>Note that invalid forward-override{} parameter syntax isn't
+ detected until the parameter is used.</p>
+ </li>
+
+ <li>
+ <p>Add another +redirect{} example: a shortcut for illumos
+ bugs.</p>
+ </li>
+
+ <li>
+ <p>Make it more obvious that many operating systems support log
+ rotation out of the box.</p>
+ </li>
+
+ <li>
+ <p>Fixed dead links. Reported by Mark Nelson in #3614557.</p>
+ </li>
+
+ <li>
+ <p>Rephrased the 'Why is the configuration so complicated?'
+ answer to be slightly less condescending. Anonymously suggested
+ in #3615122.</p>
+ </li>
+
+ <li>
+ <p>Be more explicit about accept-intercepted-requests's lack of
+ MITM support.</p>
+ </li>
+
+ <li>
+ <p>Make 'demoronizer' FAQ entries more generic.</p>
+ </li>
+
+ <li>
+ <p>Add an example hostname to the --pre-chroot-nslookup
+ description.</p>
+ </li>
+
+ <li>
+ <p>Add an example for a host pattern that matches an IP
+ address.</p>
+ </li>
+
+ <li>
+ <p>Rename the 'domain pattern' to 'host pattern' as it may
+ contain IP addresses as well.</p>
+ </li>
+
+ <li>
+ <p>Recommend forward-socks5t when using Tor. It seems to work
+ fine and modifying the Tor configuration to profit from it hasn't
+ been necessary for a while now.</p>
+ </li>
+
+ <li>
+ <p>Add another redirect{} example to stress that redirect loops
+ can and should be avoided.</p>
+ </li>
+
+ <li>
+ <p>The usual spelling and grammar fixes. Parts of them were
+ reported by Reuben Thomas in #3615276.</p>
+ </li>
+
+ <li>
+ <p>Mention the PCRS option letters T and D in the filter
+ section.</p>
+ </li>
+
+ <li>
+ <p>Clarify that handle-as-empty-doc-returns-ok is still useful
+ and will not be removed without replacement.</p>
+ </li>
+
+ <li>
+ <p>Note that security issues shouldn't be reported using the bug
+ tracker.</p>
+ </li>
+
+ <li>
+ <p>Clarify what Privoxy does if both +block{} and +redirect{}
+ apply.</p>
+ </li>
+
+ <li>
+ <p>Removed the obsolete bookmarklets section.</p>
+ </li>
+ </ul>
+ </li>
+
+ <li>
+ <p>Build system improvements:</p>
+
+ <ul>
+ <li>
+ <p>Let --with-group properly deal with secondary groups. Patch
+ submitted by Anatoly Arzhnikov in #3615187.</p>
+ </li>
+
+ <li>
+ <p>Fix web-actions target.</p>
+ </li>
+
+ <li>
+ <p>Add a web-faq target that only updates the FAQ on the
+ webserver.</p>
+ </li>
+
+ <li>
+ <p>Remove already-commented-out non-portable DOSFILTER
+ alternatives.</p>
+ </li>
+
+ <li>
+ <p>Remove the obsolete targets dok-put and dok-get.</p>
+ </li>
+
+ <li>
+ <p>Add a sf-shell target.</p>
+ </li>
+ </ul>
+ </li>
+ </ul>
+
+ <div class="SECT2">
+ <h2 class="SECT2"><a name="UPGRADERSNOTE" id="UPGRADERSNOTE">3.1. Note
+ to Upgraders</a></h2>
+
+ <p>A quick list of things to be aware of before upgrading from earlier
+ versions of <span class="APPLICATION">Privoxy</span>:</p>
+
+ <ul>
+ <li>
+ <p>The recommended way to upgrade <span class=
+ "APPLICATION">Privoxy</span> is to backup your old configuration
+ files, install the new ones, verify that <span class=
+ "APPLICATION">Privoxy</span> is working correctly and finally merge
+ back your changes using <span class="APPLICATION">diff</span> and
+ maybe <span class="APPLICATION">patch</span>.</p>
+
+ <p>There are a number of new features in each <span class=
+ "APPLICATION">Privoxy</span> release and most of them have to be
+ explicitly enabled in the configuration files. Old configuration
+ files obviously don't do that and due to syntax changes using old
+ configuration files with a new <span class=
+ "APPLICATION">Privoxy</span> isn't always possible anyway.</p>
+ </li>
+
+ <li>
+ <p>Note that some installers remove earlier versions completely,
+ including configuration files, therefore you should really save any
+ important configuration files!</p>
+ </li>
+
+ <li>
+ <p>On the other hand, other installers don't overwrite existing
+ configuration files, thinking you will want to do that
+ yourself.</p>
+ </li>
+
+ <li>
+ <p>In the default configuration only fatal errors are logged now.
+ You can change that in the <a href="config.html#DEBUG">debug
+ section</a> of the configuration file. You may also want to enable
+ more verbose logging until you verified that the new <span class=
+ "APPLICATION">Privoxy</span> version is working as expected.</p>
+ </li>
+
+ <li>
+ <p>Three other config file settings are now off by default:
+ <a href="config.html#ENABLE-REMOTE-TOGGLE">enable-remote-toggle</a>,
+ <a href=
+ "config.html#ENABLE-REMOTE-HTTP-TOGGLE">enable-remote-http-toggle</a>,
+ and <a href=
+ "config.html#ENABLE-EDIT-ACTIONS">enable-edit-actions</a>. If you
+ use or want these, you will need to explicitly enable them, and be
+ aware of the security issues involved.</p>
+ </li>
+ </ul>
+ </div>
+ </div>
+
+ <div class="NAVFOOTER">
+ <hr align="left" width="100%">
+
+ <table summary="Footer navigation table" width="100%" border="0"
+ cellpadding="0" cellspacing="0">
+ <tr>
+ <td width="33%" align="left" valign="top"><a href="installation.html"
+ accesskey="P">Prev</a></td>
+
+ <td width="34%" align="center" valign="top"><a href="index.html"
+ accesskey="H">Home</a></td>
+
+ <td width="33%" align="right" valign="top"><a href="quickstart.html"
+ accesskey="N">Next</a></td>
+ </tr>
+
+ <tr>
+ <td width="33%" align="left" valign="top">Installation</td>
+
+ <td width="34%" align="center" valign="top"> </td>
+
+ <td width="33%" align="right" valign="top">Quickstart to Using
+ Privoxy</td>
+ </tr>
+ </table>
+ </div>
+</body>
+</html>
projects / privoxy.git / blobdiff