+> 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
+> 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
+> 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
+> Fixed a crash on some Windows versions when header randomization
+ is enabled and the date couldn't be parsed.
+ </P
+></LI
+><LI
+><P
+> 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
+> 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
+> 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.