X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fsource%2Fuser-manual.sgml;h=b7493ad86cf5a47741890789920da955051f7227;hp=9314031d95ce11ec0eb676f83e3c98caa9435505;hb=58954e6a774ebf5745e9300a5629d562a9b411ba;hpb=59d134f28e0942e4464788aa3b41e8f70d3f18c8
diff --git a/doc/source/user-manual.sgml b/doc/source/user-manual.sgml
index 9314031d..b7493ad8 100644
--- a/doc/source/user-manual.sgml
+++ b/doc/source/user-manual.sgml
@@ -11,11 +11,11 @@
-
-
+
+
-
-
+
+
@@ -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.97 2009/02/14 18:01:00 fabiankeil Exp $
+$Id: user-manual.sgml,v 2.117 2010/01/11 12:56:04 fabiankeil Exp $
@@ -436,143 +437,304 @@ 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.15 beta is a bug-fix release
+ for the previous beta. The changes since 3.0.14 are:
- On most platforms, outgoing connections can be kept alive and
- reused if the server supports it. Whether or not this improves
- things depends on the connection.
+ In case of missing server data, no error message is send to the
+ client if the request arrived on a reused connection. The client
+ is then supposed to silently retry the request without bothering
+ the user. This should significantly reduce the frequency of the
+ "No server or forwarder data received" error message many users
+ reported.
- When dropping privileges, membership in supplementary groups
- is given up as well. Not doing that can lead to Privoxy running
- with more rights than necessary and violates the principle of
- least privilege. Users of the --user option are advised to update.
- Thanks to Matthias Drochner for reporting the problem,
- providing the initial patch and testing the final version.
+ More reliable detection of prematurely closed client sockets
+ with keep-alive enabled.
- Passing invalid users or groups with the --user option
- didn't lead to program exit. Regression introduced in 3.0.7.
+ FEATURE_CONNECTION_KEEP_ALIVE is decoupled from
+ FEATURE_CONNECTION_SHARING and now available on
+ all platforms.
- The match all section has been moved from default.action
- to a new file called match-all.action. As a result the
- default.action no longer needs to be touched by the user
- and can be safely overwritten by updates.
+ Improved handling of POST requests on reused connections.
+ Should fix problems with stalled connections after submitting
+ form data with some browser configurations.
- The standard.action file has been removed. Its content
- is now part of the default.action file.
+ Fixed various latency calculation issues.
- In some situations the logged content length was slightly too low.
+ Allows the client to pass NTLM authentication requests to a
+ forwarding proxy. This was already assumed and hinted to work
+ in 3.0.13 beta but actually didn't. Now it's confirmed to work
+ with IE, Firefox and Chrome.
+ Thanks to Francois Botha and Wan-Teh Chang
- Crunched requests are logged with their own log level.
- If you used "debug 1" in the past, you'll probably want
- to additionally enable "debug 1024", otherwise only passed
- requests will be logged. If you only care about crunched
- requests, simply replace "debug 1" with "debug 1024".
+ Fixed a calculation problem if receiving the server headers
+ takes more than two reads, that could cause Privoxy to terminate
+ the connection prematurely. Reported by Oliver.
- The crunch reason has been moved to the beginning of the
- crunch message. For HTTP URLs, the protocol is logged as well.
+ Compiles again on platforms such as OpenBSD and systems
+ using earlier glibc version that don't support AI_ADDRCONFIG.
+ Anonymously submitted in #2872591.
- Log messages are shortened by printing the thread id on its
- own (as opposed to putting it inside the string "Privoxy()").
+ A bunch of MS VC project files and Suse and Redhat RPM spec
+ files have been removed as they were no longer maintained for
+ quite some time.
- The config option socket-timeout has been added to control
- the time Privoxy waits for data to arrive on a socket.
+ Overly long action lines are properly rejected with a proper
+ error message. Previously they would be either rejected as
+ invalid or cause a core dump through abort().
- 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.
+ Already timed-out connections are no longer temporarily remembered.
+ They weren't reused anyway, but wasted a socket slot.
- Requests with invalid HTTP versions are rejected.
+ len refers to the number of bytes actually read which might
+ differ from the ones received. Adjust log messages accordingly.
- The template symbol @date@ can be used to include a date(1)-like
- time string. Initial patch submitted by Endre Szabo.
+ The optional JavaScript on the CGI page uses encodeURIComponent()
+ instead of escape() which doesn't encode all characters that matter.
+ Anonymously reported in #2832722.
- Responses from shoutcast servers are accepted again.
- Problem reported and fix suggested by Stefan.
+ Fix gcc45 warnings in decompress_iob().
- 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).
+ Various log message improvements.
- A "clear log" view option was added to the mingw32 version
- to clear out all of the lines in the Privoxy log window.
- Based on a patch submitted by T Ford.
+ Privoxy-Regression-Test supports redirect tests.
- The mingw32 version uses "critical sections" 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 can gather some connection statistics.
+
+
+
+
+
+
+ If you missed the previous two beta versions, you may also be
+ interested in the additional changes since 3.0.12, the
+ last stable release:
+
+
+
+
+
+
+ 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.
+
+
+
+
+ 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 mingw32 version's task bar icon is crossed out and
- the color changed to gray if Privoxy is toggled off.
+ 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'.
+
+
+
+
+ If the socket isn't reusable, Privoxy doesn't temporarily waste
+ a socket slot to remember the connection.
+
+
+
+
+ If keep-alive support is disabled but compiled in, the client's
+ Keep-Alive header is removed.
+
+
+
+
+ Fixed a bug on mingw32 where downloading large files failed if
+ keep-alive support was enabled.
+
+
+
+
+ Fixed a bug that (at least theoretically) could cause log
+ timestamps to be occasionally off by about a second.
+
+
+
+
+ The configure script respects the $PATH variable when searching
+ for groups and id.
+
+
+
+
+ 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.
+
+
+
+
+ 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.
+
+
+
+
+ Error messages in case of connection timeouts use the right
+ HTTP status code.
+
+
+
+
+ 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.
+
+
+
+
+ The error messages in case of server-connection timeouts or
+ prematurely closed server connections are now template-based.
+
+
+
+
+ If zlib support isn't compiled in, Privoxy no longer tries to
+ filter compressed content unless explicitly asked to do so.
+
+
+
+
+ In case of connections that are denied based on ACL directives,
+ the memory used for the client IP is no longer leaked.
+
+
+
+
+ Fixed another small memory leak if the client request times out
+ while waiting for client headers other than the request line.
+
+
+
+
+ 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.
+
+
+
+
+ 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
-
- For a more detailed list of changes please have a look at the ChangeLog.
-
@@ -2196,12 +2358,12 @@ for details.
Generally, an URL pattern has the form
- <domain>/<path>, where both the
- <domain> and <path> are
- optional. (This is why the special / pattern matches all
- URLs). Note that the protocol portion of the URL pattern (e.g.
- http://) should not be included in
- the pattern. This is assumed already!
+ <domain><port>/<path>, where the
+ <domain>, the <port>
+ and the <path> are optional. (This is why the special
+ / pattern matches all URLs). Note that the protocol
+ portion of the URL pattern (e.g. http://) should
+ not be included in the pattern. This is assumed already!
The pattern matching syntax is different for the domain and path parts of
@@ -2210,6 +2372,12 @@ for details.
Regular
Expressions (POSIX 1003.2).
+
+ The port part of a pattern is a decimal port number preceded by a colon
+ (:). If the domain part contains a numerical IPv6 address,
+ it has to be put into angle brackets
+ (<, >).
+
@@ -2259,6 +2427,23 @@ for details.
+
+ :8000/
+
+
+ Matches any URL pointing to TCP port 8000.
+
+
+
+
+ <2001:db8::1>/
+
+
+ Matches any URL with the host address 2001:db8::1.
+ (Note that the real URL uses plain brackets, not angle brackets.)
+
+
+ index.html
@@ -2724,6 +2909,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.
+
@@ -5220,7 +5408,7 @@ new action
reset-to-request-time overwrites the value of the
Last-Modified: header with the current time. You could use
this option together with
- hided-if-modified-since
+ hide-if-modified-since
to further customize your random range.
@@ -8502,6 +8690,69 @@ In file: user.action [ View ][ Edit ]