NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.12 User Manual"
+TITLE="Privoxy 3.0.14 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Installation"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.12 User Manual</TH
+>Privoxy 3.0.14 User Manual</TH
></TR
><TR
><TD
><P
> <SPAN
CLASS="APPLICATION"
->Privoxy 3.0.12</SPAN
-> is mainly a bugfix release:</P
+>Privoxy 3.0.14 Beta</SPAN
+> 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:</P
><P
> <P
></P
><UL
><LI
><P
-> The socket-timeout option now also works on platforms whose
- select() implementation modifies the timeout structure.
- Previously the timeout was triggered even if the connection
- didn't stall. Reported by cyberpatrol.
+> Added IPv6 support. Thanks to Petr Pisar who not only provided
+ the initial patch but also helped a lot with the integration.
</P
></LI
><LI
><P
-> The Connection: keep-alive code properly deals with files
- larger than 2GB. Previously the connection was closed too
- early.
+> Added client-side keep-alive support.
</P
></LI
><LI
><P
-> The content length for files above 2GB is logged correctly.
+> The connection sharing code is only used if the connection-sharing
+ option is enabled.
</P
></LI
><LI
><P
-> The user-manual directive on the show-status page links to
- the documentation location specified with the directive,
- not to the Privoxy website.
+> 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.
</P
></LI
><LI
><P
-> When running in daemon mode, Privoxy doesn't log anything
- to the console unless there are errors before the logfile
- has been opened.
+> The max-client-connections option has been added to restrict
+ the number of client connections below a value enforced by
+ the operating system.
</P
></LI
><LI
><P
-> The show-status page prints warnings about invalid directives
- on the same line as the directives themselves.
+> 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.
</P
></LI
><LI
><P
-> Fixed several justified (but harmless) compiler warnings,
- mostly on 64 bit platforms.
+> Setting keep-alive-timeout to 0 disables keep-alive support. Previously
+ Privoxy would claim to allow persistence but not reuse the connection.
</P
></LI
><LI
><P
-> The mingw32 version explicitly requests the default charset
- to prevent display problems with some fonts available on more
- recent Windows versions. Patch by Burberry.
+> 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.
</P
></LI
><LI
><P
-> The mingw32 version uses the Privoxy icon in the alt-tab
- windows. Patch by Burberry.
+> Fixed a crash on some Windows versions when header randomization
+ is enabled and the date couldn't be parsed.
</P
></LI
><LI
><P
-> The timestamp and the thread id is omitted in the "Fatal error"
- message box on mingw32.
+> Privoxy's keep-alive timeout for the current connection is reduced
+ to the one specified in the client's Keep-Alive header.
</P
></LI
><LI
><P
-> Fixed two related mingw32-only buffer overflows. Triggering
- them required control over the configuration file, therefore
- this isn't seen as a security issue.
+> For HTTP/1.1 requests, Privoxy implies keep-alive support by not
+ setting any Connection header instead of using 'Connection: keep-alive'.
</P
></LI
><LI
><P
-> In verbose mode, or if the new option --show-skipped-tests
- is used, Privoxy-Regression-Test logs skipped tests and the
- skip reason.
+> If the socket isn't reusable, Privoxy doesn't temporarily waste
+ a socket slot to remember the connection.
+ </P
+></LI
+><LI
+><P
+> If keep-alive support is disabled but compiled in, the client's
+ Keep-Alive header is removed.
+ </P
+></LI
+><LI
+><P
+> Fixed a bug on mingw32 where downloading large files failed if
+ keep-alive support was enabled.
+ </P
+></LI
+><LI
+><P
+> Fixed a bug that (at least theoretically) could cause log
+ timestamps to be occasionally off by about a second.
+ </P
+></LI
+><LI
+><P
+> The configure script respects the $PATH variable when searching
+ for groups and id.
+ </P
+></LI
+><LI
+><P
+> 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.
+ </P
+></LI
+><LI
+><P
+> 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.
+ </P
+></LI
+><LI
+><P
+> Error messages in case of connection timeouts use the right
+ HTTP status code.
+ </P
+></LI
+><LI
+><P
+> 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.
+ </P
+></LI
+><LI
+><P
+> The error messages in case of server-connection timeouts or
+ prematurely closed server connections are now template-based.
+ </P
+></LI
+><LI
+><P
+> If zlib support isn't compiled in, Privoxy no longer tries to
+ filter compressed content unless explicitly asked to do so.
+ </P
+></LI
+><LI
+><P
+> In case of connections that are denied based on ACL directives,
+ the memory used for the client IP is no longer leaked.
+ </P
+></LI
+><LI
+><P
+> Fixed another small memory leak if the client request times out
+ while waiting for client headers other than the request line.
+ </P
+></LI
+><LI
+><P
+> 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.
+ </P
+></LI
+><LI
+><P
+> 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
</P
></LI
></UL
projects / privoxy.git / blobdiff