1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
5 >What's New in this Release</TITLE
8 CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
10 TITLE="Privoxy 3.0.16 User Manual"
11 HREF="index.html"><LINK
14 HREF="installation.html"><LINK
16 TITLE="Quickstart to Using Privoxy"
17 HREF="quickstart.html"><LINK
20 HREF="../p_doc.css"><META
21 HTTP-EQUIV="Content-Type"
24 <LINK REL="STYLESHEET" TYPE="text/css" HREF="p_doc.css">
36 SUMMARY="Header navigation table"
45 >Privoxy 3.0.16 User Manual</TH
53 HREF="installation.html"
67 HREF="quickstart.html"
82 >3. What's New in this Release</A
88 > is a stable release.
89 The changes since 3.0.15 beta are:</P
96 > Added the config file option handle-as-empty-doc-returns-ok to
97 work around Firefox bug #492459, which causes Firefox to hang
98 if JavaScripts are blocked in certain situations. The option is
99 enabled in the default config file.
104 > Added the config option default-server-timeout to control the
105 assumed default server timeout. Since Privoxy no longer returns
106 an error message for connection resets on reused client connections,
107 assuming larger server timeout values appears to actually work
108 pretty well as long as connections aren't shared.
113 > Added optional support for FreeBSD's accf_http(9). Use the
114 configure option --enable-accept-filter to enable it.
119 > Added fancier Privoxy icons for win32. Contributed by Jeff H.
124 > In daemon mode, fd 0, 1 and 2 are bound to /dev/null.
129 > Resolve localhost using whatever address family the operating
130 system feels like. Previous betas would try to use IPv4 as this
131 is what most users expect, but this didn't work reliable on
137 > In the action lists on CGI pages, actions and their parameters are
138 no longer separated with a space. The action file parser doesn't
139 actually allow this and will throw an invalid syntax error if actions
140 and parameters in the action files are separated. Not adding the
141 spaces means copy and pasting CGI output into the action files works.
146 > The default keep-alive timeout has been reduced to 5 seconds to work
147 around hangs in clients that treat the proxy like any other host and
148 stop allowing any new connections if the "maximum number of
149 connections per host" is reached.
154 > Several webbug URLs that look like they are leading to images are now
155 blocked as image instead of empty documents. Doing the latter causes
156 WebKit-based clients to show a "missing image" icon which may mess up
162 > Accepts quoted expiration dates even though RFC 2109 10.1.2
163 doesn't seem to allow them. Reported anonymously.
168 > Don't try to forget connections if connection sharing is disabled.
169 This wasn't a real problem but caused an unnecessary log message.
174 > The still undocumented --enable-extended-host-patterns configure
175 option has a better description.
180 > Fixed an error message that would claim a write to the server
181 failed when actually writing to the client failed.
186 > Log the crunch reason before trying to write to the client.
187 The log is easier to read that way.
192 > Several log messages about client connections also mention
198 > handle-as-empty-document no longer depends on the image blocking
204 > Privoxy-Log-Parser is roughly 40% faster in highlighting mode.
209 > uagen, a Firefox User-Agent generator for Privoxy and Mozilla
210 browsers has been imported and is available in the tarballs
216 > The scripts in the tools directory treat unknown parameters
223 > If you missed the previous two beta versions, you may also be
224 interested in the additional changes since 3.0.12, the
225 last stable release:</P
232 > Added IPv6 support. Thanks to Petr Pisar who not only provided
233 the initial patch but also helped a lot with the integration.
238 > Added client-side keep-alive support.
243 > The connection sharing code is only used if the connection-sharing
249 > The latency is taken into account when evaluating whether or not to
250 reuse a connection. This should significantly reduce the number of
251 connections problems several users reported.
256 > The max-client-connections option has been added to restrict
257 the number of client connections below a value enforced by
258 the operating system.
263 > If the server doesn't specify how long the connection stays alive,
264 Privoxy errs on the safe side of caution and assumes it's only a second.
269 > Setting keep-alive-timeout to 0 disables keep-alive support. Previously
270 Privoxy would claim to allow persistence but not reuse the connection.
275 > Pipelined requests are less likely to be mistaken for the request
276 body of the previous request. Note that Privoxy still has no real
277 pipeline support and will either serialize pipelined requests or
278 drop them in which case the client has to resent them.
283 > Fixed a crash on some Windows versions when header randomization
284 is enabled and the date couldn't be parsed.
289 > Privoxy's keep-alive timeout for the current connection is reduced
290 to the one specified in the client's Keep-Alive header.
295 > For HTTP/1.1 requests, Privoxy implies keep-alive support by not
296 setting any Connection header instead of using 'Connection: keep-alive'.
301 > If the socket isn't reusable, Privoxy doesn't temporarily waste
302 a socket slot to remember the connection.
307 > If keep-alive support is disabled but compiled in, the client's
308 Keep-Alive header is removed.
313 > Fixed a bug on mingw32 where downloading large files failed if
314 keep-alive support was enabled.
319 > Fixed a bug that (at least theoretically) could cause log
320 timestamps to be occasionally off by about a second.
325 > The configure script respects the $PATH variable when searching
331 > Compressed content with extra fields couldn't be decompressed
332 and would get passed to the client unfiltered. This problem
333 has only be detected through statical analysis with clang as
334 nobody seems to be using extra fields anyway.
339 > If the server resets the Connection after sending only the headers
340 Privoxy forwards what it got to the client. Previously Privoxy
341 would deliver an error message instead.
346 > Error messages in case of connection timeouts use the right
352 > If spawning a child to handle a request fails, the client
353 gets an error message and Privoxy continues to listen for
354 new requests right away.
359 > The error messages in case of server-connection timeouts or
360 prematurely closed server connections are now template-based.
365 > If zlib support isn't compiled in, Privoxy no longer tries to
366 filter compressed content unless explicitly asked to do so.
371 > In case of connections that are denied based on ACL directives,
372 the memory used for the client IP is no longer leaked.
377 > Fixed another small memory leak if the client request times out
378 while waiting for client headers other than the request line.
383 > The client socket is kept open until the server socket has
384 been marked as unused. This should increase the chances that
385 the still-open connection will be reused for the client's next
386 request to the same destination. Note that this only matters
387 if connection-sharing is enabled.
392 > A TODO list has been added to the source tarballs to give potential
393 volunteers a better idea of what the current goals are. Donations
394 are still welcome too: http://www.privoxy.org/faq/general.html#DONATE
399 > In case of missing server data, no error message is send to the
400 client if the request arrived on a reused connection. The client
401 is then supposed to silently retry the request without bothering
402 the user. This should significantly reduce the frequency of the
403 "No server or forwarder data received" error message many users
409 > More reliable detection of prematurely closed client sockets
410 with keep-alive enabled.
415 > FEATURE_CONNECTION_KEEP_ALIVE is decoupled from
416 FEATURE_CONNECTION_SHARING and now available on
422 > Improved handling of POST requests on reused connections.
423 Should fix problems with stalled connections after submitting
424 form data with some browser configurations.
429 > Fixed various latency calculation issues.
434 > Allows the client to pass NTLM authentication requests to a
435 forwarding proxy. This was already assumed and hinted to work
436 in 3.0.13 beta but actually didn't. Now it's confirmed to work
437 with IE, Firefox and Chrome.
438 Thanks to Francois Botha and Wan-Teh Chang
443 > Fixed a calculation problem if receiving the server headers
444 takes more than two reads, that could cause Privoxy to terminate
445 the connection prematurely. Reported by Oliver.
450 > Compiles again on platforms such as OpenBSD and systems
451 using earlier glibc version that don't support AI_ADDRCONFIG.
452 Anonymously submitted in #2872591.
457 > A bunch of MS VC project files and Suse and Redhat RPM spec
458 files have been removed as they were no longer maintained for
464 > Overly long action lines are properly rejected with a proper
465 error message. Previously they would be either rejected as
466 invalid or cause a core dump through abort().
471 > Already timed-out connections are no longer temporarily remembered.
472 They weren't reused anyway, but wasted a socket slot.
477 > len refers to the number of bytes actually read which might
478 differ from the ones received. Adjust log messages accordingly.
483 > The optional JavaScript on the CGI page uses encodeURIComponent()
484 instead of escape() which doesn't encode all characters that matter.
485 Anonymously reported in #2832722.
490 > Fix gcc45 warnings in decompress_iob().
495 > Various log message improvements.
500 > Privoxy-Regression-Test supports redirect tests.
505 > Privoxy-Log-Parser can gather some connection statistics.
516 >3.1. Note to Upgraders</A
519 > A quick list of things to be aware of before upgrading from earlier
530 > The recommended way to upgrade <SPAN
533 > is to backup your old
534 configuration files, install the new ones, verify that <SPAN
538 is working correctly and finally merge back your changes using
548 > There are a number of new features in each <SPAN
552 most of them have to be explicitly enabled in the configuration
553 files. Old configuration files obviously don't do that and due
554 to syntax changes using old configuration files with a new
558 > isn't always possible anyway.
564 Note that some installers remove earlier versions completely,
565 including configuration files, therefore you should really save
566 any important configuration files!
572 On the other hand, other installers don't overwrite existing configuration
573 files, thinking you will want to do that yourself.
582 > has been merged into
591 > In the default configuration only fatal errors are logged now.
592 You can change that in the <A
593 HREF="config.html#DEBUG"
596 of the configuration file. You may also want to enable more verbose
597 logging until you verified that the new <SPAN
606 > Three other config file settings are now off by default:
608 HREF="config.html#ENABLE-REMOTE-TOGGLE"
609 >enable-remote-toggle</A
612 HREF="config.html#ENABLE-REMOTE-HTTP-TOGGLE"
613 >enable-remote-http-toggle</A
616 HREF="config.html#ENABLE-EDIT-ACTIONS"
617 >enable-edit-actions</A
619 If you use or want these, you will need to explicitly enable them, and
620 be aware of the security issues involved.
632 SUMMARY="Footer navigation table"
643 HREF="installation.html"
661 HREF="quickstart.html"
681 >Quickstart to Using Privoxy</TD