X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fsource%2Fuser-manual.sgml;h=7c262be8161f4250b41c8884c94ad16213698b2e;hp=331d1c3c0b91540ffaadacd160c5edbcc2cd7d75;hb=dde4554017f11583cb4c71ff8c84596980a17060;hpb=513c385eed6855eacbdc97c4d5815289b379c188
diff --git a/doc/source/user-manual.sgml b/doc/source/user-manual.sgml
index 331d1c3c..7c262be8 100644
--- a/doc/source/user-manual.sgml
+++ b/doc/source/user-manual.sgml
@@ -11,7 +11,7 @@
-
+
@@ -24,6 +24,7 @@
+
Privoxy">
]>
- Copyright &my-copy; 2001-2009 by
+ Copyright &my-copy; 2001-2010 by
Privoxy Developers
-$Id: user-manual.sgml,v 2.92 2009/02/12 16:08:26 fabiankeil Exp $
+$Id: user-manual.sgml,v 2.126 2010/11/06 12:55:48 fabiankeil Exp $
@@ -436,44 +437,487 @@ How to install the binary packages depends on your operating system:
What's New in this Release
- There are only a few improvements and new features since
- Privoxy 3.0.10, the last stable release:
+ Privoxy 3.0.16 is a stable release.
+ The changes since 3.0.15 beta are:
+
+
+ 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.
+ Reported by "Karsten" in #3028326.
+
+
+
+
+ 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.
+ 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.
+
+
+
+
+ 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.
+
+
+
+
+ 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.
+
+
+
+
+ The IPv6 code is enabled by default on Windows versions that support it.
+ Patch submitted by oCameLo in #2942729.
+
+
+
+
+ In mingw32 versions, the user.filter file is reachable through the
+ GUI, just like default.filter is. Feature request 3040263.
+
+
+
+
+ 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.
+
+
+
+
+ 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.
+
+
+
+
+ Privoxy logs when reading an action, filter or trust file.
+
+
+
+
+ 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.
+
+
+
+
+ CGI interface improvements:
+
+
+
+ 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.
+
+
+
+
+ Apostrophes in block messages no longer cause parse errors
+ when the blocked page is viewed with JavaScript enabled.
+ Reported by dg1727 in #3062296.
+
+
+
+
+ Fix a bunch of anchors that used underscores instead of dashes.
+
+
+
+
+ Allow to keep the client connection alive after crunching the previous request.
+ Already opened server connections can be kept alive, too.
+
+
+
+
+ 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.
+
+
+
+
+ Show the 404 CGI page if cgi_send_user_manual() is called while
+ local user manual delivery is disabled.
+
+
+
+
+
+
+ Action file improvements:
+
+
+
+ Enable user.filter by default. Suggested by David White in #3001830.
+
+
+
+
+ Block .sitestat.com/. Reported by johnd16 in #3002725.
+
+
+
+
+ Block .atemda.com/. Reported by johnd16 in #3002723.
+
+
+
+
+ Block js.adlink.net/. Reported by johnd16 in #3002720.
+
+
+
+
+ Block .analytics.yahoo.com/. Reported by johnd16 in #3002713.
+
+
+
+
+ Block sb.scorecardresearch.com, too. Reported by dg1727 in #2992652.
+
+
+
+
+ Fix problems noticed on Yahoo mail and news pages.
+
+
+
+
+ Remove the too broad yahoo section, only keeping the
+ fast-redirects exception as discussed on ijbswa-devel@.
+
+
+
+
+ Don't block adesklets.sourceforge.net. Reported in #2974204.
+
+
+
+
+ Block chartbeat ping tracking. Reported in #2975895.
+
+
+
+
+ Tag CSS and image requests with cautious and medium settings, too.
+
+
+
+
+ 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.
+
+
+
+
+ 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.
+
+
+
+
+ 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
+
+
+
+
+ ijbswa-Feature Requests-3006719 - Block 160x578 Banners.
+
+
+
+
+ Block another omniture tracking domain
+
+
+
+
+ Added a range-requests tagger.
+
+
+
+
+ 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@
+
+
+
+
+
+
+ Documentation improvements:
+
+
+
+ Explicitly mention how to match all URLs.
+
+
+
+
+ Consistently recommend socks5 in the Tor FAQ entry and mention
+ its advantage compared to socks4a. Reported by David in #2960129.
+
+
+
+
+ Slightly improve the explanation of why filtering may appear
+ slower than it is.
+
+
+
+
+ Grammar fixes for the ACL section.
+
+
+
+
- The mingw32 version uses mutex locks now which prevents
- log message corruption under load. As a side effect,
- the "no thread-safe PRNG" warning could be removed as well.
+ Privoxy-Log-Parser improvements:
+
+
+
+ Also gather statistics for blocked and redirected requests.
+
+
+
+
+ Provide the percentage of keep-alive offers the client accepted.
+
+
+
+
+ Add a --url-statistics-threshold option.
+
+
+
+
+ Also gather statistics for ressources, methods, and HTTP versions
+ used by the client.
+
+
+
+
+ Add a --host-statistics-threshold option to also gather
+ statistics about how many request where made per host.
+
+
+
+
+ Fix a bug in handle_loglevel_header() where a 'scan: ' got lost.
+
+
+
+
+ Add a --shorten-thread-ids option to replace the thread id with
+ a decimal number.
+
+
+
+
+ Accept and ignore: Looks like we got the last chunk together
+ with the server headers. We better stop reading.
+
+
+
+
+ Accept and ignore: Continue hack in da house.
+
+
+
+
+ Accept and higlight: Rejecting connection from 10.0.0.2.
+ Maximum number of connections reached.
+
+
+
+
+ Accept and highlight: Loading actions file: /usr/local/etc/privoxy/default.action
+
+
+
+
+ Accept and highlight: Loading filter file: /usr/local/etc/privoxy/default.filter
+
+
+
+
+ Accept and highlight: Killed all-caps Host header line: HOST: bestproxydb.com
+
+
+
+
+ Accept and highlight: Reducing expected bytes to 0. Marking
+ the server socket tainted after throwing 4 bytes away.
+
+
+
+
+ Accept: Merged multiple header lines to: 'X-FORWARDED-PROTO: http X-HOST: 127.0.0.1'
+
+
- Support for remote toggling is controlled by the configure
- option --disable-toggle only. In previous versions it also
- depended on the action editor and thus configuring with the
- --disable-editor option would disable remote toggling support
- as well.
+ Code cleanups:
+
+
+
+ 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.
+
+
+
+
+ Garbage-collect request_contains_null_bytes().
+
+
+
+
+ Ditch redundant code in unload_configfile().
+
+
+
+
+ Ditch LogGetURLUnderCursor() which doesn't seem to be used anywhere.
+
+
+
+
+ In write_socket(), remove the write-only variable write_len in
+ an ifdef __OS2__ block. Spotted by cppcheck.
+
+
+
+
+ In connect_to(), don't declare the variable 'flags' on OS/2 where
+ it isn't used. Spotted by cppcheck.
+
+
+
+
+ Limit the scope of various variables. Spotted by cppcheck.
+
+
+
+
+ In add_to_iob(), turn an interestingly looking for loop into a
+ boring while loop.
+
+
+
+
+ Code cleanup in preparation for external filters.
+
+
+
+
+ In listen_loop(), mention the socket on which we accepted the
+ connection, not just the source IP address.
+
+
+
+
+ In write_socket(), also log the socket we're writing to.
+
+
+
+
+ In log_error(), assert that escaped characters get logged
+ completely or not at all.
+
+
+
+
+ In log_error(), assert that ival and sval have reasonable values.
+ There's no reason not to abort() if they don't.
+
+
+
+
+ Remove an incorrect cgi_error_unknown() call in a
+ cannnot-happen-situation in send_crunch_response().
+
+
+
+
+ Clean up white-space in http_response definition and
+ move the crunch_reason to the beginning.
+
+
+
+
+ Turn http_response.reason into an enum and rename it
+ to http_response.crunch_reason.
+
+
+
+
+ Silence a 'gcc (Debian 4.3.2-1.1) 4.3.2' warning on i686 GNU/Linux.
+
+
- The hide-forwarded-for-headers action has been replaced with
- the change-x-forwarded-for{} action which can also be used to
- add X-Forwarded-For headers. The latter functionality already
- existed in Privoxy versions prior to 3.0.7 but has been removed
- as it was often used unintentionally (by not using the
- hide-forwarded-for-headers action).
+ GNUmakefile improvements:
+
+
+
+ Use $(SSH) instead of ssh, so one only needs to specify a username once.
+
+
+
+
+ Removed references to the action feedback thingy that hasn't been
+ working for years.
+
+
+
+
+ Consistently use shell.sourceforge.net instead of shell.sf.net so
+ one doesn't need to check server fingerprints twice.
+
+
+
+
+ Removed GNUisms in the webserver and webactions targets so they
+ work with standard tar.
+
+
-
- For a more detailed list of changes please have a look at the ChangeLog.
-
@@ -543,18 +987,6 @@ How to install the binary packages depends on your operating system:
-
-
- The filter-client-headers and
- filter-server-headers actions that were introduced with
- Privoxy 3.0.5 to apply content filters to
- the headers have been removed and replaced with new actions.
- See the What's New section above.
-
-
-
-
-
-
The first of our specialized sections is concerned with fragile
sites, i.e. sites that require minimum interference, because they are either
@@ -5953,36 +6403,10 @@ mail.google.com
.scan.co.uk
-
-
The fast-redirects
- action, which we enabled per default above, breaks some sites. So disable
- it for popular sites where we know it misbehaves:
+ action, which may have been enabled in match-all.action,
+ breaks some sites. So disable it for popular sites where we know it misbehaves:
@@ -6002,8 +6426,8 @@ edit.*.yahoo.com
be blocked, a substitute image can be sent, rather than an HTML page.
Contacting the remote site to find out is not an option, since it
would destroy the loading time advantage of banner blocking, and it
- would feed the advertisers (in terms of money and
- information). We can mark any URL as an image with the handle-as-image action,
and marking all URLs that end in a known image file extension is a
good start:
@@ -8459,6 +8883,111 @@ In file: user.action [ View ][ Edit ]