- 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.
+ - Remove an unreasonable parameter limit in the CGI interface. The new
+ parameter limit depends on the memory available and is currently unlikely
+ to be reachable, due to other limits in both Privoxy and common clients.
+ Reported by Andrew on ijbswa-users@.
+ - Decrease the chances of parse failures after requests with unsupported
+ methods were sent to the CGI interface.
- Action file improvements:
- Remove the comment that indicated that updated default.action versions
is at best useless.
- Use privoxy_tolower() instead of vanilla tolower() with manual casting of
the argument.
+ - Catch ssplit() failures in parse_cgi_parameters().
- Privoxy-Regression-Test:
- Add an 'Overwrite condition' directive to skip any matching tests before
- Privoxy-Log-Parser:
- Improve the --statistics performance by skipping sanity checks for input
- that shouldn't affect the results anyway. In my non-scientific benchmarks
- this reduces the runtime by about 45%. Also add a --strict-checks option
+ that shouldn't affect the results anyway. Add a --strict-checks option
that enables some of the checks again, just in case anybody cares.
- - Accept and highlight: Stopping to watch the client socket. There's already
- another request waiting.
- - Cleanup variable initialization in print_non_clf_message().
- - Properly highlight the new log messages from get_request_line().
- - Let get_percentage() show 0 of x as 0% even if x is 0 as well.
- - Accept and ignore: Enlisting (sorted|left-over) header ...
- - Accept the shiny new LOG_LEVEL_ACTIONS.
- - Accept and highlight: Closing client socket 5. Keep-alive: 0, Socket
- alive: 1. Data available: 0.
- - Stop suppressing messages about accepted client connections and highlight
- them properly.
- - Accept and highlight: Accepted connection from 10.0.0.1 on socket 5.
- - Accept and highlight: Continuing buffering server headers from socket 5.
- Bytes most recently read: 498.
- - Accept and highlight: Client request 4 arrived in time on socket 7.
- - Accept and highlight: Closing client socket 8. Keep-alive: 1. Socket
- alive: 0. Data available: 0. Configuration file change detected: 0.
- Requests received: 11.
- - Accept and highlight: Drained 180 bytes before closing socket 6.
- - Accept and highlight the extended log message for client sockets.
- - Accept and highlight: Tainting client socket 7 due to unread data.
- - Accept and highlight: Optimistically sending 318 bytes of client
- headers intended for www.privoxy.org.
- - Accept and highlight: Client request 8 has been pipelined on socket 7 and
- the socket is still alive.
- - Accept: There better be a request body.
- - Accept and highlight: Shifting 360 pipelined bytes by 360 bytes.
- - Accept and highlight: Multiple Content-Type headers detected. Removing and
- ignoring: Content-Type: text/html.
+ - The distribution of client requests per connection is included in the
+ --statistic output.
+ - The --accept-unknown-messages option has been removed and the behavior
+ is now the default.
+ - Accept and (mostly) highlight new log messages introduced with
+ Privoxy 3.0.20.
- uagen:
- - Bump generated Firefox version to 16.
-
-- CGI interface improvements & bug fixes:
- - Remove an unreasonable parameter limit in parse_cgi_parameters(). The new
- parameter limit depends on the memory available and is currently unlikely
- to be reachable, due to other limits in both Privoxy and common clients.
- Reported by Andrew on ijbswa-users@.
- - Catch ssplit() failures in parse_cgi_parameters().
- - Deal with unsupported methods sent to the CGI pages by discarding any
- data following the headers.
+ - Bump generated Firefox version to 17.
- GNUmakefile improvements:
- The dok-tidy target no longer taints documents with a tidy-mark
projects / privoxy.git / blobdiff