-<!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.16 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.16 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
-> <SPAN
-CLASS="APPLICATION"
->Privoxy 3.0.15 beta</SPAN
-> is a bug-fix release
- for the previous beta. The changes since 3.0.14 are:</P
-><P
-> <P
-></P
-><UL
-><LI
-><P
-> In case of missing server data, no error message is send to the
- client if the request arrived on a reused connection. The client
- is then supposed to silently retry the request without bothering
- the user. This should significantly reduce the frequency of the
- "No server or forwarder data received" error message many users
- reported.
- </P
-></LI
-><LI
-><P
-> More reliable detection of prematurely closed client sockets
- with keep-alive enabled.
- </P
-></LI
-><LI
-><P
-> FEATURE_CONNECTION_KEEP_ALIVE is decoupled from
- FEATURE_CONNECTION_SHARING and now available on
- all platforms.
- </P
-></LI
-><LI
-><P
-> Improved handling of POST requests on reused connections.
- Should fix problems with stalled connections after submitting
- form data with some browser configurations.
- </P
-></LI
-><LI
-><P
-> Fixed various latency calculation issues.
- </P
-></LI
-><LI
-><P
-> Allows the client to pass NTLM authentication requests to a
- forwarding proxy. This was already assumed and hinted to work
- in 3.0.13 beta but actually didn't. Now it's confirmed to work
- with IE, Firefox and Chrome.
- Thanks to Francois Botha and Wan-Teh Chang
- </P
-></LI
-><LI
-><P
-> Fixed a calculation problem if receiving the server headers
- takes more than two reads, that could cause Privoxy to terminate
- the connection prematurely. Reported by Oliver.
- </P
-></LI
-><LI
-><P
-> Compiles again on platforms such as OpenBSD and systems
- using earlier glibc version that don't support AI_ADDRCONFIG.
- Anonymously submitted in #2872591.
- </P
-></LI
-><LI
-><P
-> A bunch of MS VC project files and Suse and Redhat RPM spec
- files have been removed as they were no longer maintained for
- quite some time.
- </P
-></LI
-><LI
-><P
-> Overly long action lines are properly rejected with a proper
- error message. Previously they would be either rejected as
- invalid or cause a core dump through abort().
- </P
-></LI
-><LI
-><P
-> Already timed-out connections are no longer temporarily remembered.
- They weren't reused anyway, but wasted a socket slot.
- </P
-></LI
-><LI
-><P
-> len refers to the number of bytes actually read which might
- differ from the ones received. Adjust log messages accordingly.
- </P
-></LI
-><LI
-><P
-> The optional JavaScript on the CGI page uses encodeURIComponent()
- instead of escape() which doesn't encode all characters that matter.
- Anonymously reported in #2832722.
- </P
-></LI
-><LI
-><P
-> Fix gcc45 warnings in decompress_iob().
- </P
-></LI
-><LI
-><P
-> Various log message improvements.
- </P
-></LI
-><LI
-><P
-> Privoxy-Regression-Test supports redirect tests.
- </P
-></LI
-><LI
-><P
-> Privoxy-Log-Parser can gather some connection statistics.
- </P
-></LI
-></UL
-></P
-><P
-> If you missed the previous two beta versions, you may also be
- interested in the additional changes since 3.0.12, the
- last stable release:</P
-><P
-> <P
-></P
-><UL
-><LI
-><P
-> Added IPv6 support. Thanks to Petr Pisar who not only provided
- the initial patch but also helped a lot with the integration.
- </P
-></LI
-><LI
-><P
-> Added client-side keep-alive support.
- </P
-></LI
-><LI
-><P
-> The connection sharing code is only used if the connection-sharing
- option is enabled.
- </P
-></LI
-><LI
-><P
-> The latency is taken into account when evaluating whether or not to
- reuse a connection. This should significantly reduce the number of
- connections problems several users reported.
- </P
-></LI
-><LI
-><P
-> The max-client-connections option has been added to restrict
- the number of client connections below a value enforced by
- the operating system.
- </P
-></LI
-><LI
-><P
-> If the server doesn't specify how long the connection stays alive,
- Privoxy errs on the safe side of caution and assumes it's only a second.
- </P
-></LI
-><LI
-><P
-> Setting keep-alive-timeout to 0 disables keep-alive support. Previously
- Privoxy would claim to allow persistence but not reuse the connection.
- </P
-></LI
-><LI
-><P
-> Pipelined requests are less likely to be mistaken for the request
- body of the previous request. Note that Privoxy still has no real
- pipeline support and will either serialize pipelined requests or
- drop them in which case the client has to resent them.
- </P
-></LI
-><LI
-><P
-> Fixed a crash on some Windows versions when header randomization
- is enabled and the date couldn't be parsed.
- </P
-></LI
-><LI
-><P
-> Privoxy's keep-alive timeout for the current connection is reduced
- to the one specified in the client's Keep-Alive header.
- </P
-></LI
-><LI
-><P
-> For HTTP/1.1 requests, Privoxy implies keep-alive support by not
- setting any Connection header instead of using 'Connection: keep-alive'.
- </P
-></LI
-><LI
-><P
-> If the socket isn't reusable, Privoxy doesn't temporarily waste
- a socket slot to remember the connection.
- </P
-></LI
-><LI
-><P
-> If keep-alive support is disabled but compiled in, the client's
- Keep-Alive header is removed.
- </P
-></LI
-><LI
-><P
-> Fixed a bug on mingw32 where downloading large files failed if
- keep-alive support was enabled.
- </P
-></LI
-><LI
-><P
-> Fixed a bug that (at least theoretically) could cause log
- timestamps to be occasionally off by about a second.
- </P
-></LI
-><LI
-><P
-> The configure script respects the $PATH variable when searching
- for groups and id.
- </P
-></LI
-><LI
-><P
-> Compressed content with extra fields couldn't be decompressed
- and would get passed to the client unfiltered. This problem
- has only be detected through statical analysis with clang as
- nobody seems to be using extra fields anyway.
- </P
-></LI
-><LI
-><P
-> If the server resets the Connection after sending only the headers
- Privoxy forwards what it got to the client. Previously Privoxy
- would deliver an error message instead.
- </P
-></LI
-><LI
-><P
-> Error messages in case of connection timeouts use the right
- HTTP status code.
- </P
-></LI
-><LI
-><P
-> If spawning a child to handle a request fails, the client
- gets an error message and Privoxy continues to listen for
- new requests right away.
- </P
-></LI
-><LI
-><P
-> The error messages in case of server-connection timeouts or
- prematurely closed server connections are now template-based.
- </P
-></LI
-><LI
-><P
-> If zlib support isn't compiled in, Privoxy no longer tries to
- filter compressed content unless explicitly asked to do so.
- </P
-></LI
-><LI
-><P
-> In case of connections that are denied based on ACL directives,
- the memory used for the client IP is no longer leaked.
- </P
-></LI
-><LI
-><P
-> Fixed another small memory leak if the client request times out
- while waiting for client headers other than the request line.
- </P
-></LI
-><LI
-><P
-> The client socket is kept open until the server socket has
- been marked as unused. This should increase the chances that
- the still-open connection will be reused for the client's next
- request to the same destination. Note that this only matters
- if connection-sharing is enabled.
- </P
-></LI
-><LI
-><P
-> A TODO list has been added to the source tarballs to give potential
- volunteers a better idea of what the current goals are. Donations
- are still welcome too: http://www.privoxy.org/faq/general.html#DONATE
- </P
-></LI
-></UL
-></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