1 Announcing Privoxy v.3.0.13 beta
2 -----------------------------------------------------------------
4 Privoxy 3.0.13 beta introduces IPv6 support, improved keep-alive
5 support and a bunch of minor improvements.
7 See http://www.privoxy.org/3.0.13/user-manual/whatsnew.html for details.
9 --------------------------------------------------------------------
11 --------------------------------------------------------------------
12 *** Version 3.0.13 beta ***
14 - Added IPv6 support. Thanks to Petr Pisar who not only provided
15 the initial patch but also helped a lot with the integration.
16 - Added client-side keep-alive support. This should also allow
17 NTLM authentication through Privoxy, but this hasn't been
19 - The connection sharing code is only used if the connection-sharing
21 - The max-client-connections option has been added to restrict
22 the number of client connections below a value enforced by
24 - Fixed a regression reintroduced in 3.0.12 that could cause
25 crashes on mingw32 if header date randomization was enabled.
26 - Compressed content with extra fields couldn't be decompressed
27 and would get passed to the client unfiltered. This problem
28 has only be detected through statical analysis with clang as
29 nobody seems to be using extra fields anyway.
30 - If the server resets the Connection after sending only the headers
31 Privoxy forwards what it got to the client. Previously Privoxy
32 would deliver an error message instead.
33 - Error messages in case of connection timeouts use the right
35 - If spawning a child to handle a request fails, the client
36 gets an error message and Privoxy continues to listen for
37 new requests right away.
38 - The error messages in case of server-connection timeouts or
39 prematurely closed server connections are now template-based.
40 - If zlib support isn't compiled in, Privoxy no longer tries to
41 filter compressed content unless explicitly asked to do so.
42 - In case of connections that are denied based on ACL directives,
43 the memory used for the client IP is no longer leaked.
44 - Fixed another small memory leak if the client request times out
45 while waiting for client headers other than the request line.
46 - The client socket is kept open until the server socket has
47 been marked as unused. This should increase the chances that
48 the still-open connection will be reused for the client's next
49 request to the same destination. Note that this only matters
50 if connection-sharing is enabled.
51 - A TODO list has been added to the source tarballs to give potential
52 volunteers a better idea of what the current goals are.
54 -----------------------------------------------------------------
56 -----------------------------------------------------------------
58 Privoxy is a non-caching web proxy with advanced filtering capabilities for
59 enhancing privacy, modifying web page data and HTTP headers, controlling
60 access, and removing ads and other obnoxious Internet junk. Privoxy has a
61 flexible configuration and can be customized to suit individual needs and
62 tastes. It has application for both stand-alone systems and multi-user
65 Privoxy is Free Software and licensed under the GPL2.
67 Privoxy is an associated project of Software in the Public Interest (SPI).
68 Donations are welcome: http://www.privoxy.org/faq/general.html#DONATE
70 At present, Privoxy is known to run on Windows(95, 98, ME, 2000,
71 XP, Vista), Linux (Ubuntu, RedHat, SuSE, Debian, Fedora, Gentoo and
72 others), Mac OSX, OS/2, AmigaOS, FreeBSD, NetBSD, OpenBSD, Solaris, and
73 various other flavors of Unix.
75 In addition to the core features of ad blocking and cookie management,
76 Privoxy provides many supplemental features, that give the end-user
77 more control, more privacy and more freedom:
80 * Supports "Connection: keep-alive". Outgoing connections can be kept
81 alive independently from the client.
85 * Supports tagging which allows to change the behaviour based on client
88 * Can be run as an "intercepting" proxy, which obviates the need to
89 configure browsers individually.
91 * Sophisticated actions and filters for manipulating both server and
94 * Can be chained with other proxies.
96 * Integrated browser based configuration and control utility at
97 http://config.privoxy.org/ (shortcut: http://p.p/). Browser-based
98 tracing of rule and filter effects. Remote toggling.
100 * Web page filtering (text replacements, removes banners based on size,
101 invisible "web-bugs", JavaScript and HTML annoyances, pop-up windows,
104 * Modularized configuration that allows for standard settings and user
105 settings to reside in separate files, so that installing updated actions
106 files won't overwrite individual user settings.
108 * Support for Perl Compatible Regular Expressions in the configuration
109 files, and a more sophisticated and flexible configuration syntax.
113 * Bypass many click-tracking scripts (avoids script redirection).
115 * Multi-threaded (POSIX and native threads).
117 * User-customizable HTML templates for most proxy-generated pages (e.g.
120 * Auto-detection and re-reading of config file changes.
122 * Improved signal handling, and a true daemon mode (Unix).
124 * Every feature now controllable on a per-site or per-location basis,
125 configuration more powerful and versatile over-all.
129 http://sourceforge.net/project/showfiles.php?group_id=11118
132 http://www.privoxy.org/
135 - Privoxy Developers <ijbswa-developers@lists.sourceforge.net>