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.17 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.17 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.16 stable are:</P
96 > Fixed last-chunk-detection for responses where the content was small
97 enough to be read with the body, causing Privoxy to wait for the
98 end of the content until the server closed the connection or the
99 request timed out. Reported by "Karsten" in #3028326.
104 > Responses with status code 204 weren't properly detected as body-less
105 like RFC2616 mandates. Like the previous bug, this caused Privoxy to
106 wait for the end of the content until the server closed the connection
107 or the request timed out. Fixes #3022042 and #3025553, reported by a
108 user with no visible name. Most likely also fixes a bunch of other
109 AJAX-related problem reports that got closed in the past due to
110 insufficient information and lack of feedback.
115 > Fixed an ACL bug that made it impossible to build a blacklist.
116 Usually the ACL directives are used in a whitelist, which worked
117 as expected, but blacklisting is still useful for public proxies
118 where one only needs to deny known abusers access.
123 > Added LOG_LEVEL_RECEIVED to log the not-yet-parsed data read from the
124 network. This should make debugging various parsing issues a lot easier.
129 > The IPv6 code is enabled by default on Windows versions that support it.
130 Patch submitted by oCameLo in #2942729.
135 > In mingw32 versions, the user.filter file is reachable through the
136 GUI, just like default.filter is. Feature request 3040263.
141 > Added the configure option --enable-large-file-support to set a few
142 defines that are required by platforms like GNU/Linux to support files
143 larger then 2GB. Mainly interesting for users without proper logfile
149 > Logging with "debug 16" no longer stops at the first nul byte which is
150 pretty useless. Non-printable characters are replaced with their hex value
151 so the result can't span multiple lines making parsing them harder then
157 > Privoxy logs when reading an action, filter or trust file.
162 > Fixed incorrect regression test markup which caused a test in
163 3.0.16 to fail while Privoxy itself was working correctly.
164 While Privoxy accepts hide-referer, too, the action name is actually
165 hide-referrer which is also the name used one the final results page,
166 where the test expected the alias.
171 > CGI interface improvements:
177 > In finish_http_response(), continue to add the 'Connection: close'
178 header if the client connection will not be kept alive.
179 Anonymously pointed out in #2987454.
184 > Apostrophes in block messages no longer cause parse errors
185 when the blocked page is viewed with JavaScript enabled.
186 Reported by dg1727 in #3062296.
191 > Fix a bunch of anchors that used underscores instead of dashes.
196 > Allow to keep the client connection alive after crunching the previous request.
197 Already opened server connections can be kept alive, too.
202 > In cgi_show_url_info(), don't forget to prefix URLs that only contain
203 http:// or https:// in the path. Fixes #2975765 reported by Adam Piggott.
208 > Show the 404 CGI page if cgi_send_user_manual() is called while
209 local user manual delivery is disabled.
218 > Action file improvements:
224 > Enable user.filter by default. Suggested by David White in #3001830.
229 > Block .sitestat.com/. Reported by johnd16 in #3002725.
234 > Block .atemda.com/. Reported by johnd16 in #3002723.
239 > Block js.adlink.net/. Reported by johnd16 in #3002720.
244 > Block .analytics.yahoo.com/. Reported by johnd16 in #3002713.
249 > Block sb.scorecardresearch.com, too. Reported by dg1727 in #2992652.
254 > Fix problems noticed on Yahoo mail and news pages.
259 > Remove the too broad yahoo section, only keeping the
260 fast-redirects exception as discussed on ijbswa-devel@.
265 > Don't block adesklets.sourceforge.net. Reported in #2974204.
270 > Block chartbeat ping tracking. Reported in #2975895.
275 > Tag CSS and image requests with cautious and medium settings, too.
280 > Don't handle view.atdmt.com as image. It's used for click-throughs
281 so users should be able to "go there anyway".
282 Reported by Adam Piggott in #2975927.
287 > Also let the refresh-tags filter remove invalid refresh tags where
288 the 'url=' part is missing. Anonymously reported in #2986382.
289 While at it, update the description to mention the fact that only
290 refresh tags with refresh times above 9 seconds are covered.
295 > javascript needs to be blocked with +handle-as-empty-document to
296 work around Firefox bug 492459. So move .js blockers from
297 +block{Might be a web-bug.} -handle-as-empty-document to
298 +block{Might be a web-bug.} +handle-as-empty-document.
303 > ijbswa-Feature Requests-3006719 - Block 160x578 Banners.
308 > Block another omniture tracking domain.
313 > Added a range-requests tagger.
318 > Added two sections to get Flickr's Ajax interface working with
319 default pre-settings. If you change the configuration to block
320 cookies by default, you'll need additional exceptions.
321 Reported by Mathias Homann in #3101419 and by Patrick on ijbswa-users@.
330 > Documentation improvements:
336 > Explicitly mention how to match all URLs.
341 > Consistently recommend socks5 in the Tor FAQ entry and mention
342 its advantage compared to socks4a. Reported by David in #2960129.
347 > Slightly improve the explanation of why filtering may appear
353 > Grammar fixes for the ACL section.
358 > Fixed a link to the 'intercepting' entry and add another one.
363 > Rename the 'Other' section to 'Mailing Lists' and reword it
364 to make it clear that nobody is forced to use the trackers
369 > Note that 'anonymously' posting on the trackers may not always
375 > Suggest to enable debug 32768 when suspecting parsing problems.
384 > Privoxy-Log-Parser improvements:
390 > Gather statistics for ressources, methods, and HTTP versions
396 > Also gather statistics for blocked and redirected requests.
401 > Provide the percentage of keep-alive offers the client accepted.
406 > Add a --url-statistics-threshold option.
411 > Add a --host-statistics-threshold option to also gather
412 statistics about how many request where made per host.
417 > Fix a bug in handle_loglevel_header() where a 'scan: ' got lost.
422 > Add a --shorten-thread-ids option to replace the thread id with
428 > Accept and ignore: Looks like we got the last chunk together
429 with the server headers. We better stop reading.
434 > Accept and ignore: Continue hack in da house.
439 > Accept and higlight: Rejecting connection from 10.0.0.2.
440 Maximum number of connections reached.
445 > Accept and highlight: Loading actions file: /usr/local/etc/privoxy/default.action
450 > Accept and highlight: Loading filter file: /usr/local/etc/privoxy/default.filter
455 > Accept and highlight: Killed all-caps Host header line: HOST: bestproxydb.com
460 > Accept and highlight: Reducing expected bytes to 0. Marking
461 the server socket tainted after throwing 4 bytes away.
466 > Accept: Merged multiple header lines to: 'X-FORWARDED-PROTO: http X-HOST: 127.0.0.1'
481 > Remove the next member from the client_state struct. Only the main
482 thread needs access to all client states so give it its own struct.
487 > Garbage-collect request_contains_null_bytes().
492 > Ditch redundant code in unload_configfile().
497 > Ditch LogGetURLUnderCursor() which doesn't seem to be used anywhere.
502 > In write_socket(), remove the write-only variable write_len in
503 an ifdef __OS2__ block. Spotted by cppcheck.
508 > In connect_to(), don't declare the variable 'flags' on OS/2 where
509 it isn't used. Spotted by cppcheck.
514 > Limit the scope of various variables. Spotted by cppcheck.
519 > In add_to_iob(), turn an interestingly looking for loop into a
525 > Code cleanup in preparation for external filters.
530 > In listen_loop(), mention the socket on which we accepted the
531 connection, not just the source IP address.
536 > In write_socket(), also log the socket we're writing to.
541 > In log_error(), assert that escaped characters get logged
542 completely or not at all.
547 > In log_error(), assert that ival and sval have reasonable values.
548 There's no reason not to abort() if they don't.
553 > Remove an incorrect cgi_error_unknown() call in a
554 cannnot-happen-situation in send_crunch_response().
559 > Clean up white-space in http_response definition and
560 move the crunch_reason to the beginning.
565 > Turn http_response.reason into an enum and rename it
566 to http_response.crunch_reason.
571 > Silence a 'gcc (Debian 4.3.2-1.1) 4.3.2' warning on i686 GNU/Linux.
576 > Fix white-space in a log message in remove_chunked_transfer_coding().
577 While at it, add a note that the message doesn't seem to
578 be entirely correct and should be improved later on.
587 > GNUmakefile improvements:
593 > Use $(SSH) instead of ssh, so one only needs to specify a username once.
598 > Removed references to the action feedback thingy that hasn't been
604 > Consistently use shell.sourceforge.net instead of shell.sf.net so
605 one doesn't need to check server fingerprints twice.
610 > Removed GNUisms in the webserver and webactions targets so they
611 work with standard tar.
626 >3.1. Note to Upgraders</A
629 > A quick list of things to be aware of before upgrading from earlier
640 > The recommended way to upgrade <SPAN
643 > is to backup your old
644 configuration files, install the new ones, verify that <SPAN
648 is working correctly and finally merge back your changes using
658 > There are a number of new features in each <SPAN
662 most of them have to be explicitly enabled in the configuration
663 files. Old configuration files obviously don't do that and due
664 to syntax changes using old configuration files with a new
668 > isn't always possible anyway.
674 Note that some installers remove earlier versions completely,
675 including configuration files, therefore you should really save
676 any important configuration files!
682 On the other hand, other installers don't overwrite existing configuration
683 files, thinking you will want to do that yourself.
692 > has been merged into
701 > In the default configuration only fatal errors are logged now.
702 You can change that in the <A
703 HREF="config.html#DEBUG"
706 of the configuration file. You may also want to enable more verbose
707 logging until you verified that the new <SPAN
716 > Three other config file settings are now off by default:
718 HREF="config.html#ENABLE-REMOTE-TOGGLE"
719 >enable-remote-toggle</A
722 HREF="config.html#ENABLE-REMOTE-HTTP-TOGGLE"
723 >enable-remote-http-toggle</A
726 HREF="config.html#ENABLE-EDIT-ACTIONS"
727 >enable-edit-actions</A
729 If you use or want these, you will need to explicitly enable them, and
730 be aware of the security issues involved.
742 SUMMARY="Footer navigation table"
753 HREF="installation.html"
771 HREF="quickstart.html"
791 >Quickstart to Using Privoxy</TD