1 Announcing Privoxy v.3.0.14 beta
2 -----------------------------------------------------------------
4 Privoxy 3.0.14 beta is a bugfix-release for the previous beta
5 which introduced IPv6 support, improved keep-alive support and
6 a bunch of minor improvements.
8 See http://www.privoxy.org/3.0.14/user-manual/whatsnew.html for details.
10 --------------------------------------------------------------------
12 --------------------------------------------------------------------
13 *** Version 3.0.14 beta ***
15 - The latency is taken into account when evaluating whether or not to
16 reuse a connection. This should significantly reduce the number of
17 connections problems several users reported.
18 - If the server doesn't specify how long the connection stays alive,
19 Privoxy errs on the safe side of caution and assumes it's only a second.
20 - The error pages for connection timeouts or missing server data use a
21 Last-Modified date in the past. Retry attempts are detected and Privoxy
22 removes the If-Modified-Since header to prevent the server from responding
23 with status code 304 in which case the client would reuse the error message.
24 - Setting keep-alive-timeout to 0 disables keep-alive support. Previously
25 Privoxy would claim to allow persistence but not reuse the connection.
26 - Pipelined requests are less likely to be mistaken for the request
27 body of the previous request. Note that Privoxy still has no real
28 pipeline support and will either serialize pipelined requests or
29 drop them in which case the client has to resent them.
30 - Fixed a crash on some Windows versions when header randomization
31 is enabled and the date couldn't be parsed.
32 - Privoxy's keep-alive timeout for the current connection is reduced
33 to the one specified in the client's Keep-Alive header.
34 - For HTTP/1.1 requests, Privoxy implies keep-alive support by not
35 setting any Connection header instead of using 'Connection: keep-alive'.
36 - If the socket isn't reusable, Privoxy doesn't temporarily waste
37 a socket slot to remember the connection.
38 - If keep-alive support is disabled but compiled in, the client's
39 Keep-Alive header is removed.
40 - Fixed a bug on mingw32 where downloading large files failed if
41 keep-alive support was enabled.
42 - Fixed a bug that (at least theoretically) could cause log
43 timestamps to be occasionally off by about a second.
44 - No Proxy-Connection header if added if there already is one.
45 - The configure script respects the $PATH variable when searching
48 *** Version 3.0.13 beta ***
50 - Added IPv6 support. Thanks to Petr Pisar who not only provided
51 the initial patch but also helped a lot with the integration.
52 - Added client-side keep-alive support.
53 - The connection sharing code is only used if the connection-sharing
55 - The max-client-connections option has been added to restrict
56 the number of client connections below a value enforced by
58 - Fixed a regression reintroduced in 3.0.12 that could cause
59 crashes on mingw32 if header date randomization was enabled.
60 - Compressed content with extra fields couldn't be decompressed
61 and would get passed to the client unfiltered. This problem
62 has only be detected through statical analysis with clang as
63 nobody seems to be using extra fields anyway.
64 - If the server resets the Connection after sending only the headers
65 Privoxy forwards what it got to the client. Previously Privoxy
66 would deliver an error message instead.
67 - Error messages in case of connection timeouts use the right
69 - If spawning a child to handle a request fails, the client
70 gets an error message and Privoxy continues to listen for
71 new requests right away.
72 - The error messages in case of server-connection timeouts or
73 prematurely closed server connections are now template-based.
74 - If zlib support isn't compiled in, Privoxy no longer tries to
75 filter compressed content unless explicitly asked to do so.
76 - In case of connections that are denied based on ACL directives,
77 the memory used for the client IP is no longer leaked.
78 - Fixed another small memory leak if the client request times out
79 while waiting for client headers other than the request line.
80 - The client socket is kept open until the server socket has
81 been marked as unused. This should increase the chances that
82 the still-open connection will be reused for the client's next
83 request to the same destination. Note that this only matters
84 if connection-sharing is enabled.
85 - A TODO list has been added to the source tarballs to give potential
86 volunteers a better idea of what the current goals are.
88 -----------------------------------------------------------------
90 -----------------------------------------------------------------
92 Privoxy is a non-caching web proxy with advanced filtering capabilities for
93 enhancing privacy, modifying web page data and HTTP headers, controlling
94 access, and removing ads and other obnoxious Internet junk. Privoxy has a
95 flexible configuration and can be customized to suit individual needs and
96 tastes. It has application for both stand-alone systems and multi-user
99 Privoxy is Free Software and licensed under the GPL2.
101 Privoxy is an associated project of Software in the Public Interest (SPI).
102 Donations are welcome: http://www.privoxy.org/faq/general.html#DONATE
104 At present, Privoxy is known to run on Windows(95, 98, ME, 2000,
105 XP, Vista), Linux (Ubuntu, RedHat, SuSE, Debian, Fedora, Gentoo and
106 others), Mac OSX, OS/2, AmigaOS, FreeBSD, NetBSD, OpenBSD, Solaris, and
107 various other flavors of Unix.
109 In addition to the core features of ad blocking and cookie management,
110 Privoxy provides many supplemental features, that give the end-user
111 more control, more privacy and more freedom:
114 * Supports "Connection: keep-alive". Outgoing connections can be kept
115 alive independently from the client. Currently not available on all
118 * Supports IPv6, provided the operating system does so too,
119 and the configure script detects it.
121 * Supports tagging which allows to change the behaviour based on client
124 * Can be run as an "intercepting" proxy, which obviates the need to
125 configure browsers individually.
127 * Sophisticated actions and filters for manipulating both server and
130 * Can be chained with other proxies.
132 * Integrated browser based configuration and control utility at
133 http://config.privoxy.org/ (shortcut: http://p.p/). Browser-based
134 tracing of rule and filter effects. Remote toggling.
136 * Web page filtering (text replacements, removes banners based on size,
137 invisible <quote>web-bugs</quote> and HTML annoyances, etc.)
139 * Modularized configuration that allows for standard settings and user
140 settings to reside in separate files, so that installing updated actions
141 files won't overwrite individual user settings.
143 * Support for Perl Compatible Regular Expressions in the configuration
144 files, and a more sophisticated and flexible configuration syntax.
148 * Bypass many click-tracking scripts (avoids script redirection).
150 * User-customizable HTML templates for most proxy-generated pages (e.g.
153 * Auto-detection and re-reading of config file changes.
155 * Most features are controllable on a per-site or per-location basis.
159 http://sourceforge.net/project/showfiles.php?group_id=11118
162 http://www.privoxy.org/
165 - Privoxy Developers <ijbswa-developers@lists.sourceforge.net>