X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fsource%2Fuser-manual.sgml;h=ea67d35f29d4e7e6abf3b0b4ef598fb28b5713aa;hp=f60bbaebb6603bd2633bddb8d6aff9fd2fccec69;hb=b13c15a5b84e9ca8e1477b16951262fb6f4b36ac;hpb=d85ed748a397a98d5d33aade5f8cf5ed719dac1c
diff --git a/doc/source/user-manual.sgml b/doc/source/user-manual.sgml
index f60bbaeb..ea67d35f 100644
--- a/doc/source/user-manual.sgml
+++ b/doc/source/user-manual.sgml
@@ -11,11 +11,11 @@
-
-
+
+
-
-
+
+
@@ -34,9 +34,9 @@
This file belongs into
ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
- $Id: user-manual.sgml,v 2.108 2009/07/18 15:49:23 fabiankeil Exp $
+ $Id: user-manual.sgml,v 2.127 2010/11/10 21:48:54 fabiankeil Exp $
- Copyright (C) 2001-2009 Privoxy Developers http://www.privoxy.org/
+ Copyright (C) 2001-2010 Privoxy Developers http://www.privoxy.org/
See LICENSE.
========================================================================
@@ -55,12 +55,12 @@
- Copyright &my-copy; 2001-2009 by
+ Copyright &my-copy; 2001-2010 by
Privoxy Developers
-$Id: user-manual.sgml,v 2.108 2009/07/18 15:49:23 fabiankeil Exp $
+$Id: user-manual.sgml,v 2.127 2010/11/10 21:48:54 fabiankeil Exp $
@@ -437,180 +437,482 @@ How to install the binary packages depends on your operating system:
What's New in this Release
- Privoxy 3.0.14 Beta is a bugfix-release
- for the previous beta which introduced IPv6 support, improved keep-alive
- support and a bunch of minor improvements. The changes since 3.0.12:
+ Privoxy 3.0.17 is a stable release.
+ The changes since 3.0.16 stable are:
-
-
- Added IPv6 support. Thanks to Petr Pisar who not only provided
- the initial patch but also helped a lot with the integration.
-
-
-
-
- Added client-side keep-alive support. This should also allow
- NTLM authentication through Privoxy, but this hasn't been
- confirmed yet.
-
-
-
-
- The connection sharing code is only used if the connection-sharing
- option is enabled.
-
-
-
-
- The latency is taken into account when evaluating whether or not to
- reuse a connection. This should significantly reduce the number of
- connections problems several users reported.
-
-
-
-
- The max-client-connections option has been added to restrict
- the number of client connections below a value enforced by
- the operating system.
-
-
-
-
- If the server doesn't specify how long the connection stays alive,
- Privoxy errs on the safe side of caution and assumes it's only a second.
-
-
-
-
- Setting keep-alive-timeout to 0 disables keep-alive support. Previously
- Privoxy would claim to allow persistence but not reuse the connection.
-
-
-
-
- Pipelined requests are less likely to be mistaken for the request
- body of the previous request. Note that Privoxy still has no real
- pipeline support and will either serialize pipelined requests or
- drop them in which case the client has to resent them.
-
-
-
-
- Fixed a crash on some Windows versions when header randomization
- is enabled and the date couldn't be parsed.
-
-
-
-
- Privoxy's keep-alive timeout for the current connection is reduced
- to the one specified in the client's Keep-Alive header.
-
-
-
+
- For HTTP/1.1 requests, Privoxy implies keep-alive support by not
- setting any Connection header instead of using 'Connection: keep-alive'.
+ 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.
- If the socket isn't reusable, Privoxy doesn't temporarily waste
- a socket slot to remember the connection.
+ 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.
- If keep-alive support is disabled but compiled in, the client's
- Keep-Alive header is removed.
+ 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.
- Fixed a bug on mingw32 where downloading large files failed if
- keep-alive support was enabled.
+ 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.
- Fixed a bug that (at least theoretically) could cause log
- timestamps to be occasionally off by about a second.
+ The IPv6 code is enabled by default on Windows versions that support it.
+ Patch submitted by oCameLo in #2942729.
- The configure script respects the $PATH variable when searching
- for groups and id.
+ In mingw32 versions, the user.filter file is reachable through the
+ GUI, just like default.filter is. Feature request 3040263.
- Compressed content with extra fields couldn't be decompressed
- and would get passed to the client unfiltered. This problem
- has only be detected through statical analysis with clang as
- nobody seems to be using extra fields anyway.
+ 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.
- If the server resets the Connection after sending only the headers
- Privoxy forwards what it got to the client. Previously Privoxy
- would deliver an error message instead.
+ 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.
- Error messages in case of connection timeouts use the right
- HTTP status code.
+ Privoxy logs when reading an action, filter or trust file.
- If spawning a child to handle a request fails, the client
- gets an error message and Privoxy continues to listen for
- new requests right away.
+ 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.
- The error messages in case of server-connection timeouts or
- prematurely closed server connections are now template-based.
+ 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.
+
+
- If zlib support isn't compiled in, Privoxy no longer tries to
- filter compressed content unless explicitly asked to do so.
+ 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@
+
+
- In case of connections that are denied based on ACL directives,
- the memory used for the client IP is no longer leaked.
+ 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.
+
+
- Fixed another small memory leak if the client request times out
- while waiting for client headers other than the request line.
+ 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'
+
+
- The client socket is kept open until the server socket has
- been marked as unused. This should increase the chances that
- the still-open connection will be reused for the client's next
- request to the same destination. Note that this only matters
- if connection-sharing is enabled.
+ 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.
+
+
- A TODO list has been added to the source tarballs to give potential
- volunteers a better idea of what the current goals are. Donations
- are still welcome too: http://www.privoxy.org/faq/general.html#DONATE
+ 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.
+
+
@@ -2308,6 +2610,15 @@ for details.
+
+ /
+
+
+ Matches any URL because there's no requirement for either the
+ domain or the path to match anything.
+
+
+ :8000/
@@ -2790,6 +3101,9 @@ for details.
HTTP headers are, you definitely don't need to worry about this
one.
+
+ Headers added by this action are not modified by other actions.
+
@@ -3977,9 +4291,10 @@ problem-host.example.com
Filtering requires buffering the page content, which may appear to
slow down page rendering since nothing is displayed until all content has
- passed the filters. (It does not really take longer, but seems that way
- since the page is not incrementally displayed.) This effect will be more
- noticeable on slower connections.
+ passed the filters. (The total time until the page is completely rendered
+ doesn't change much, but it may be perceived as slower since the page is
+ not incrementally displayed.)
+ This effect will be more noticeable on slower connections.
Rolling your own
@@ -8568,6 +8883,63 @@ In file: user.action [ View ][ Edit ]