- <p>Clarify the effect of compiling Privoxy with zlib support
- Suggested by dg1727 in #3423782.</p>
- </li>
-
- <li>
- <p>Point out that the SourceForge messaging system works like a
- black hole and should thus not be used to contact individual
- developers.</p>
- </li>
-
- <li>
- <p>Mention some of the problems one can experience when not
- explicitly configuring an IP addresses as listen address.</p>
- </li>
-
- <li>
- <p>Explicitly mention that hostnames can be used instead of IP
- addresses for the listen-address, that only the first address
- returned will be used and what happens if the address is invalid.
- Requested by Calestyo in #3302213.</p>
- </li>
- </ul>
- </li>
-
- <li>
- <p>Log message improvements:</p>
-
- <ul>
- <li>
- <p>If only the server connection is kept alive, do not pretend to
- wait for a new client request.</p>
- </li>
-
- <li>
- <p>Remove a superfluous log message in forget_connection()</p>
- </li>
-
- <li>
- <p>In chat(), properly report missing server responses as such
- instead of calling them empty</p>
- </li>
-
- <li>
- <p>In forwarded_connect(), fix a log message nobody should ever
- see</p>
- </li>
-
- <li>
- <p>Fix a log message in socks5_connect(), a failed write
- operation was logged as failed read operation</p>
- </li>
-
- <li>
- <p>Let load_one_actions_file() properly complain about a missing
- '{' at the beginning of the file Simply stating that a line is
- invalid isn't particularly helpful.</p>
- </li>
-
- <li>
- <p>Do not claim to listen on a socket until Privoxy actually
- does. Patch submitted by Petr Pisar #3354485</p>
- </li>
-
- <li>
- <p>Prevent a duplicated LOG_LEVEL_CLF message when sending out
- the "no-server-data" response</p>
- </li>
-
- <li>
- <p>Also log the client socket when dropping a connection.</p>
- </li>
-
- <li>
- <p>Include the destination host in the 'Request ... marked for
- blocking. limit-connect{...} doesn't allow CONNECT ...' message
- Patch submitted by Saperski in #3296250.</p>
- </li>
-
- <li>
- <p>Prevent a duplicated log message if none of the resolved IP
- addresses were reachable</p>
- </li>
-
- <li>
- <p>In connect_to(), do not pretend to retry if
- forwarded-connect-retries is zero or unset.</p>
- </li>
-
- <li>
- <p>When a specified user or group can't be found, put the name in
- single-quotes when logging it.</p>
- </li>
-
- <li>
- <p>In rfc2553_connect_to(), explain getnameinfo() errors
- better.</p>
- </li>
-
- <li>
- <p>Remove a useless log message in chat()</p>
- </li>
-
- <li>
- <p>When retrying to connect, also log the maximum number of
- connection attempts</p>
- </li>
-
- <li>
- <p>Rephrase a log message in compile_dynamic_pcrs_job_list().
- Divide the error code and its meaning with a colon. Call the pcrs
- job dynamic and not the filter. Filters may contain dynamic and
- non-dynamic pcrs jobs at the same time. Only mention the name of
- the filter or tagger, but don't claim it's a filter when it could
- be a tagger.</p>
- </li>
-
- <li>
- <p>In a fatal error message in load_one_actions_file(), cover
- both URL and TAG patterns.</p>
- </li>
-
- <li>
- <p>In pcrs_strerror(), properly report unknown positive error
- code values as such. Previously they were handled like 0 (no
- error).</p>
- </li>
-
- <li>
- <p>In compile_dynamic_pcrs_job_list(), also log the actual error
- code as pcrs_strerror() doesn't handle all errors reported by
- pcre</p>
- </li>
-
- <li>
- <p>Don't bother trying to continue chatting if the client didn't
- ask for it. Reduces log noise a bit.</p>
- </li>
-
- <li>
- <p>Make two fatal error message in load_one_actions_file() more
- descriptive</p>
- </li>
-
- <li>
- <p>In cgi_send_user_manual(), log when rejecting a file name due
- to '/' or '..'</p>
- </li>
-
- <li>
- <p>In load_file(), log a message if opening a file failed The CGI
- error message alone isn't too helpful.</p>
- </li>
-
- <li>
- <p>In connection_destination_matches(), improve two log messages
- to help understand why the destinations don't match.</p>
- </li>
-
- <li>
- <p>Rephrase a log message in serve(). Client request arrival
- should be differentiated from closed client connections now.</p>
- </li>
-
- <li>
- <p>In serve(), log if a client connection isn't reused due to a
- configuration file change.</p>
- </li>
-
- <li>
- <p>Let mark_server_socket_tainted() always mark the server socket
- tainted, just don't talk about it in cases where it has no
- effect. It doesn't change Privoxy's behaviour, but makes
- understanding the log file easier.</p>
- </li>
- </ul>
- </li>
-
- <li>
- <p>configure:</p>
-
- <ul>
- <li>
- <p>Added a --disable-ipv6-support switch for platforms where
- support is detected but doesn't actually work.</p>