- Two new actions <link
- linkend="server-header-tagger">server-header-tagger</link>
- and <link
- linkend="client-header-tagger">client-header-tagger</link>
- that can be used to create arbitrary <quote>tags</quote>
- based on client and server headers.
- These <quote>tags</quote> can then subsequently be used
- to control the other actions used for the current request,
- greatly increasing &my-app;'s flexibility and selectivity. See <link
- linkend="tag-pattern">tag patterns</link> for more information on tags.
- </para>
- </listitem>
-
- <listitem>
- <para>
- Header filtering is done with dedicated header filters now. As a result
- the actions <quote>filter-client-headers</quote> and <quote>filter-server-headers</quote>
- that were introduced with <application>Privoxy 3.0.5</application> to apply
- content filters to the headers have been removed.
- See the new actions <link
- linkend="server-header-filter">server-header-filter</link>
- and <link
- linkend="client-header-filter">client-header-filter</link> for details.
- </para>
- </listitem>
- <listitem>
- <para>
- There are four new options for the main <filename>config</filename> file:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
- <link
- linkend="allow-cgi-request-crunching">allow-cgi-request-crunching</link>
- which allows requests for Privoxy's internal CGI pages to be
- blocked, redirected or (un)trusted like ordinary requests.
- </para>
- </listitem>
- <listitem>
- <para>
- <link
- linkend="split-large-forms">split-large-forms</link>
- that will work around a browser bug that caused IE6 and IE7 to
- ignore the Submit button on the Privoxy's edit-actions-for-url CGI
- page.
- </para>
- </listitem>
- <listitem>
- <para>
- <link
- linkend="accept-intercepted-requests">accept-intercepted-requests</link>
- which allows to combine Privoxy with any packet filter to create an
- intercepting proxy for HTTP/1.1 requests (and for HTTP/1.0 requests
- with Host header set). This means clients can be forced to use
- &my-app; even if their proxy settings are configured differently.
- </para>
- </listitem>
- <listitem>
- <para>
- <link
- linkend="templdir">templdir</link>
- to designate an alternate location for &my-app;'s
- locally customized CGI templates so that
- these are not overwritten during upgrades.
- </para>
- </listitem>
- </itemizedlist>
+ Fixed last-chunk-detection for responses where the content was small
+ enough to be read with the body, causing Privoxy to wait for the
+ end of the content until the server closed the connection or the
+ request timed out. Reported by "Karsten" in #3028326.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Responses with status code 204 weren't properly detected as body-less
+ like RFC2616 mandates. Like the previous bug, this caused Privoxy to
+ wait for the end of the content until the server closed the connection
+ or the request timed out. Fixes #3022042 and #3025553, reported by a
+ user with no visible name. Most likely also fixes a bunch of other
+ AJAX-related problem reports that got closed in the past due to
+ insufficient information and lack of feedback.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Fixed an ACL bug that made it impossible to build a blacklist.
+ Usually the ACL directives are used in a whitelist, which worked
+ as expected, but blacklisting is still useful for public proxies
+ where one only needs to deny known abusers access.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Added LOG_LEVEL_RECEIVED to log the not-yet-parsed data read from the
+ network. This should make debugging various parsing issues a lot easier.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The IPv6 code is enabled by default on Windows versions that support it.
+ Patch submitted by oCameLo in #2942729.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In mingw32 versions, the user.filter file is reachable through the
+ GUI, just like default.filter is. Feature request 3040263.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Added the configure option --enable-large-file-support to set a few
+ defines that are required by platforms like GNU/Linux to support files
+ larger then 2GB. Mainly interesting for users without proper logfile
+ management.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Logging with "debug 16" no longer stops at the first nul byte which is
+ pretty useless. Non-printable characters are replaced with their hex value
+ so the result can't span multiple lines making parsing them harder then
+ necessary.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Privoxy logs when reading an action, filter or trust file.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Fixed incorrect regression test markup which caused a test in
+ 3.0.16 to fail while Privoxy itself was working correctly.
+ While Privoxy accepts hide-referer, too, the action name is actually
+ hide-referrer which is also the name used one the final results page,
+ where the test expected the alias.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ CGI interface improvements:
+ <itemizedlist>
+ <listitem>
+ <para>
+ In finish_http_response(), continue to add the 'Connection: close'
+ header if the client connection will not be kept alive.
+ Anonymously pointed out in #2987454.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Apostrophes in block messages no longer cause parse errors
+ when the blocked page is viewed with JavaScript enabled.
+ Reported by dg1727 in #3062296.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Fix a bunch of anchors that used underscores instead of dashes.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Allow to keep the client connection alive after crunching the previous request.
+ Already opened server connections can be kept alive, too.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In cgi_show_url_info(), don't forget to prefix URLs that only contain
+ http:// or https:// in the path. Fixes #2975765 reported by Adam Piggott.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Show the 404 CGI page if cgi_send_user_manual() is called while
+ local user manual delivery is disabled.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Action file improvements:
+ <itemizedlist>
+ <listitem>
+ <para>
+ Enable user.filter by default. Suggested by David White in #3001830.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Block .sitestat.com/. Reported by johnd16 in #3002725.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Block .atemda.com/. Reported by johnd16 in #3002723.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Block js.adlink.net/. Reported by johnd16 in #3002720.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Block .analytics.yahoo.com/. Reported by johnd16 in #3002713.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Block sb.scorecardresearch.com, too. Reported by dg1727 in #2992652.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Fix problems noticed on Yahoo mail and news pages.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Remove the too broad yahoo section, only keeping the
+ fast-redirects exception as discussed on ijbswa-devel@.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Don't block adesklets.sourceforge.net. Reported in #2974204.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Block chartbeat ping tracking. Reported in #2975895.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Tag CSS and image requests with cautious and medium settings, too.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Don't handle view.atdmt.com as image. It's used for click-throughs
+ so users should be able to "go there anyway".
+ Reported by Adam Piggott in #2975927.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Also let the refresh-tags filter remove invalid refresh tags where
+ the 'url=' part is missing. Anonymously reported in #2986382.
+ While at it, update the description to mention the fact that only
+ refresh tags with refresh times above 9 seconds are covered.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ javascript needs to be blocked with +handle-as-empty-document to
+ work around Firefox bug 492459. So move .js blockers from
+ +block{Might be a web-bug.} -handle-as-empty-document to
+ +block{Might be a web-bug.} +handle-as-empty-document.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ ijbswa-Feature Requests-3006719 - Block 160x578 Banners.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Block another omniture tracking domain.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Added a range-requests tagger.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Added two sections to get Flickr's Ajax interface working with
+ default pre-settings. If you change the configuration to block
+ cookies by default, you'll need additional exceptions.
+ Reported by Mathias Homann in #3101419 and by Patrick on ijbswa-users@.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Documentation improvements:
+ <itemizedlist>
+ <listitem>
+ <para>
+ Explicitly mention how to match all URLs.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Consistently recommend socks5 in the Tor FAQ entry and mention
+ its advantage compared to socks4a. Reported by David in #2960129.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Slightly improve the explanation of why filtering may appear
+ slower than it is.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Grammar fixes for the ACL section.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Fixed a link to the 'intercepting' entry and add another one.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Rename the 'Other' section to 'Mailing Lists' and reword it
+ to make it clear that nobody is forced to use the trackers
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Note that 'anonymously' posting on the trackers may not always
+ be possible.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Suggest to enable debug 32768 when suspecting parsing problems.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Privoxy-Log-Parser improvements:
+ <itemizedlist>
+ <listitem>
+ <para>
+ Gather statistics for ressources, methods, and HTTP versions
+ used by the client.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Also gather statistics for blocked and redirected requests.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Provide the percentage of keep-alive offers the client accepted.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Add a --url-statistics-threshold option.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Add a --host-statistics-threshold option to also gather
+ statistics about how many request where made per host.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Fix a bug in handle_loglevel_header() where a 'scan: ' got lost.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Add a --shorten-thread-ids option to replace the thread id with
+ a decimal number.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Accept and ignore: Looks like we got the last chunk together
+ with the server headers. We better stop reading.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Accept and ignore: Continue hack in da house.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Accept and higlight: Rejecting connection from 10.0.0.2.
+ Maximum number of connections reached.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Accept and highlight: Loading actions file: /usr/local/etc/privoxy/default.action
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Accept and highlight: Loading filter file: /usr/local/etc/privoxy/default.filter
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Accept and highlight: Killed all-caps Host header line: HOST: bestproxydb.com
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Accept and highlight: Reducing expected bytes to 0. Marking
+ the server socket tainted after throwing 4 bytes away.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Accept: Merged multiple header lines to: 'X-FORWARDED-PROTO: http X-HOST: 127.0.0.1'
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Code cleanups:
+ <itemizedlist>
+ <listitem>
+ <para>
+ Remove the next member from the client_state struct. Only the main
+ thread needs access to all client states so give it its own struct.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Garbage-collect request_contains_null_bytes().
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Ditch redundant code in unload_configfile().
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Ditch LogGetURLUnderCursor() which doesn't seem to be used anywhere.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In write_socket(), remove the write-only variable write_len in
+ an ifdef __OS2__ block. Spotted by cppcheck.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In connect_to(), don't declare the variable 'flags' on OS/2 where
+ it isn't used. Spotted by cppcheck.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Limit the scope of various variables. Spotted by cppcheck.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In add_to_iob(), turn an interestingly looking for loop into a
+ boring while loop.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Code cleanup in preparation for external filters.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In listen_loop(), mention the socket on which we accepted the
+ connection, not just the source IP address.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In write_socket(), also log the socket we're writing to.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In log_error(), assert that escaped characters get logged
+ completely or not at all.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ In log_error(), assert that ival and sval have reasonable values.
+ There's no reason not to abort() if they don't.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Remove an incorrect cgi_error_unknown() call in a
+ cannot-happen-situation in send_crunch_response().
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Clean up white-space in http_response definition and
+ move the crunch_reason to the beginning.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Turn http_response.reason into an enum and rename it
+ to http_response.crunch_reason.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Silence a 'gcc (Debian 4.3.2-1.1) 4.3.2' warning on i686 GNU/Linux.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Fix white-space in a log message in remove_chunked_transfer_coding().
+ While at it, add a note that the message doesn't seem to
+ be entirely correct and should be improved later on.
+ </para>