It was broken since their introduction in 2009. The calculated latency
for most connections would be 0 in which case the timeout detection
failed to account for the real latency.
- - Fix a Windows-specific log viewer thread safety issue.
- Reported by Tim H. in #3525694.
- - Let fatal_error() write to the logfile right away, before showing the
- Windows-specific error message which blocks until the user acknowledges
- it, thus complicating automatic error detection.
- Reported by Adriaan in #3593603.
- - Fix the --disable-ipv6-support configure option for the Windows platform.
- - In socks5_connect(), do not try to print a negative number of socks
- response bytes if the read() for the socks5 negotiation failed
- completely. It's an API violation and can trigger an assert() in debug
- builds with "debug 2" enabled. Except for the assert(), log_error()
- already handled negative %N values gracefully so this commit only makes a
- difference for debug builds.
- - Fix an assertion that could cause debug builds to abort() if a filter
- contained nul bytes in the replacement text.
- Reject URLs with invalid port. Previously they were parsed incorrectly and
characters between the port number and the first slash were silently
dropped as shown by curl test 187.
- The default-server-timeout and socket-timeout directives accept 0 as
valid value.
+ - Fix a race condition on Windows that could cause Privoxy to become
+ unresponsive after toggling it on or off through the taskbar icon.
+ Reported by Tim H. in #3525694.
+ - Fix the compilation on Windows when configured without IPv6 support.
+ - Fix an assertion that could cause debug builds to abort() in case of
+ socks5 connection failures with "debug 2" enabled.
+ - Fix an assertion that could cause debug builds to abort() if a filter
+ contained nul bytes in the replacement text.
- General improvements:
- Significantly improved keep-alive support for both client and server
properly.
- Allow closing curly braces as part of action values as long as they are
escaped.
+ - On Windows, the logfile is now written before showing the GUI error
+ message which blocks until the user acknowledges it.
+ Reported by Adriaan in #3593603.
- Action file improvements:
- Remove the comment that indicated that updated versions of this file are