- <p>Move the site-specific documentation block before the generic one. While most Privoxy installations
- don't have a site-specific documentation block, in cases were it exists it's likely to be more relevant
- than the generic one. Showing it first makes it less likely that users stop reading before they reach it,
- especially on pages that don't fit on the screen.</p>
+ <p>Only show crunch statistics if crunches were detected.</p>
+ </li>
+ <li>
+ <p>Warn if the request counts differ.</p>
+ </li>
+ <li>
+ <p>Generate statistics if the log only contains LOG_LEVEL_CLF messages so it can be used with vanilla
+ webserver logs. Previously Privoxy-specific "Request:" messages were required.</p>
+ </li>
+ <li>
+ <p>Align the client-HTTP-version distribution like other distributions</p>
+ </li>
+ <li>
+ <p>Bump version to 0.9.1</p>
+ </li>
+ <li>
+ <p>Include status code distribution in the stats.</p>
+ </li>
+ <li>
+ <p>Let the statistics include the size of the content Privoxy transferred excluding HTTP headers.</p>
+ </li>
+ <li>
+ <p>Get with the program and expect all requests to be logged with LOG_LEVEL_REQUEST. It's no longer
+ necessary to count both LOG_LEVEL_REQUEST and LOG_LEVEL_CRUNCH messages to get the total number of
+ requests.</p>
+ </li>
+ <li>
+ <p>Leverage the LOG_LEVEL_CLF message to gather statistics that where previously taken from
+ LOG_LEVEL_HEADER lines. This results in less confusing results if https inspection is enabled in which case
+ there are two LOG_LEVEL_HEADER lines with request lines. Sponsored by: Robert Klemme</p>
+ </li>
+ <li>
+ <p>Properly highlight the filter results message. Previously a brace got lost.</p>
+ </li>
+ <li>
+ <p>Prefer the number of CLF lines to get the total number of requests as it works with older Privoxy
+ versions as well.</p>