X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Fwhatsnew.html;h=63d9c0058815a28e325cb525fe6de74e1c27fa61;hb=d718332b42f884d9c3c2fd0cfa9b83f4973c6971;hp=3e38ba0c37e37b019189b98fbfa9afb44ed2323e;hpb=07cf496b6edcbd3cf315ec7c48f2c94be27357b1;p=privoxy.git diff --git a/doc/webserver/user-manual/whatsnew.html b/doc/webserver/user-manual/whatsnew.html index 3e38ba0c..63d9c005 100644 --- a/doc/webserver/user-manual/whatsnew.html +++ b/doc/webserver/user-manual/whatsnew.html @@ -1,1008 +1,493 @@ -
- -Privoxy 3.0.18 User Manual | +Privoxy 3.0.30 User Manual | ||||
---|---|---|---|---|---|
Prev | - +Prev | - - | Next | +Next |
Privoxy 3.0.18 is a stable release. - The changes since 3.0.17 stable are:
- +Privoxy 3.0.29 fixes a couple of memory leaks and introduces https inspection + which allows to filter encrypted requests and responses.
+Changes in Privoxy 3.0.29 stable:
Bug fixes:
- +Security/Reliability:
Fix a logic bug that could cause Privoxy to reuse a tainted - server socket. It could happen for server sockets that got - tainted by a server-header-tagger-induced block, in which case - Privoxy doesn't necessarily read the whole server response. If - keep-alive was enabled and the request following the blocked one - was to the same host and using the same forwarding settings, - Privoxy would send it on the tainted server socket. While the - server would simply treat it as a pipelined request, Privoxy - would later on fail to properly parse the server's response as it - would try to parse the unread data from the first response as - server headers for the second one. Regression introduced in - 3.0.17.
-When implying keep-alive in client_connection(), remember that - the client didn't Fixes a regression introduced in 3.0.13 that - would cause Privoxy to wait for additional client requests after - receiving a HTTP/1.1 request with "Connection: close" set and - connection sharing enabled. With clients like curl which - terminates the client connection after detecting that the whole - body has been received it doesn't really matter, but with clients - like FreeBSD's fetch the client connection would be kept open - until it timed out.
-Fix a subtle race condition between - prepare_csp_for_next_request() and sweep() A thread preparing - itself for the next client request could briefly appear to be - inactive. If all other threads were already using more recent - files, the thread could get its files swept away under its feet. - I've only seen it while stress testing in valgrind while touching - action files in a loop. It's unlikely to have caused any actual - problems in the real world.
+Fixed memory leaks when a response is buffered and the buffer limit is reached or Privoxy is running out + of memory. Commits bbd53f1010b and 4490d451f9b. OVE-20201118-0001. Sponsored by: Robert Klemme
General improvements:
- -Privoxy can (re)compress buffered content before delivering it - to the client. Disabled by default as most users wouldn't benefit - from it.
-The +fast-redirects{check-decoded-url} action checks URL - segments separately. If there are other parameters behind the - redirect URL, this makes it unnecessary to cut them of by - additionally using a +redirect{} pcrs command. Initial patch - submitted by Jamie Zawinski in #3429848.
-Properly deal with FEATURE_TOGGLE being disabled
-Adjust url_code_map[] so spaces are replaced with %20 instead - of '+' While '+' can be used by client's submitting form data, - this is not actually what Privoxy is using the lookups for. This - is more of a cosmetic issue and doesn't fix any actual problems - I'm aware of.
-When compiled without FEATURE_FAST_REDIRECTS, do not silently - ignore +fast-redirect{} directives
-Added a workaround for GNU libc's strptime() reporting - negative year values when the parsed year is only specified with - two digits. On affected systems cookies with such a date would - not be turned into session cookies by the +session-cookies-only - action. Reported by Vaeinoe in #3403560
+Fixed a memory leak in the show-status CGI handler when no action files are configured. Commit + c62254a686. OVE-20201118-0002. Sponsored by: Robert Klemme
When loading action sections, verify that the referenced - filters exist Currently missing filters only result in an error - message, but eventually the severity will be upgraded to - fatal.
+Fixed a memory leak in the show-status CGI handler when no filter files are configured. Commit + 1b1370f7a8a. OVE-20201118-0003. Sponsored by: Robert Klemme
Allow to bind to multiple separate addresses. Patch set - submitted by Petr Pisar in #3354485.
+Fixes a memory leak when client tags are active. Commit 245e1cf32. OVE-20201118-0004. Sponsored by: + Robert Klemme
Set socket_error to errno if connecting fails in - rfc2553_connect_to() Previously rejected direct connections could - be incorrectly reported as DNS issues.
+Fixed a memory leak if multiple filters are executed and the last one is skipped due to a pcre error. + Commit 5cfb7bc8fe. OVE-20201118-0005.
Fixed bind failures with certain GNU libc versions if no - non-loopback IP address has been configured on the system. This - is mainly an issue if the system is using DHCP and Privoxy is - started before the network is completely configured. Reported by - Raphael Marichez in #3349356. Additional insight from Petr - Pisar.
+Prevent an unlikely dereference of a NULL-pointer that could result in a crash if + accept-intercepted-requests was enabled, Privoxy failed to get the request destination from the Host header + and a memory allocation failed. Commit 7530132349. CID 267165. OVE-20201118-0006.
Disable filters if SDCH compression is used unless filtering - is forced. If SDCH was combined with a supported compression - algorithm, we'd previously try to decompress it, when successful - apply the enabled filters and ditch the Content-Encoding header - even though the SDCH compression wasn't removed. Reported by - zebul666 in #3225863.
+Fixed memory leaks in the client-tags CGI handler when client tags are configured and memory allocations + fail. Commit cf5640eb2a. CID 267168. OVE-20201118-0007.
Privoxy log messages now use the ISO 8601 date format - %Y-%m-%d. It's only slightly longer than the old format, but - contains the full date including the year and allows sorting by - date (when grepping in multiple log files) without hassle.
-Make a copy of the --user value and only mess with that when - splitting user and group. On some operating systems modifying the - value directly is reflected in the output of ps and friends and - can be misleading. Reported by zepard in #3292710.
-If forwarded-connect-retries is set, only retry if the we are - actually forwarding the request. Previously direct connections - would be retried as well.
-Fixed a small memory leak when retrying connection
-Remove an incorrect assertion in - compile_dynamic_pcrs_job_list() It could be triggered by a pcrs - job with an invalid pcre pattern (for example one that contains a - lone quantifier).
+Fixed memory leaks in the show-status CGI handler when memory allocations fail. Commit 064eac5fd0 and + commit fdee85c0bf3. CID 305233. OVE-20201118-0008.
Action file improvements:
- +General improvements:
Moved the site-specific block pattern section below the one - for the generic patterns so for requests that are matched in - both, the block reason for the domain is shown which is usually - more useful than showing the one for the generic pattern.
-Add a (disabled) section to block various Facebook tracking - URLs Reported by Dan Stahlke in #3421764.
-Add a (disabled) section to rewrite and redirect - click-tracking URLs used on news.google.com Reported by Dan - Stahlke in #3421755.
+Added experimental https inspection support which allows to filter https traffic. To enable it, install + MbedTLS and configure with --with-mbedtls, or install OpenSSL or LibreSSL and configure with + --with-openssl. Afterwards configure the directives in section 7 of the config file and enable the + +https-inspection action. Initial MbedTLS-based code contributed by Vaclav Svec, initial OpenSSL support + contributed by Maxim Antonov. With help from Nedzad Hrnjica and Ho+ Ho+ Ho+. Integration and improvements + sponsored by Robert Klemme.
Unblock linuxcounter.net/ Reported by Dan Stahlke in - #3422612.
+pcrs: Request JIT compilation if it's supported and the filter isn't dynamic. This can speed up + filtering.
Block 'www91.intel.com/' which is used by Omniture. Reported - by Adam Piggott in #3167370.
+Added support for Brotli decompression. Sponsored by: Robert Klemme
Disable the handle-as-empty-doc-returns-ok option and mark it - as deprecated. Reminded by tceverling in #2790091.
+Added FEATURE_EXTENDED_STATISTICS to gather statistics for block reasons and filter executions. To + enable it, configure with --enable-extended-statistics and visit http://config.privoxy.org/show-status. + Sponsored by: Robert Klemme
Add ".ivwbox.de/" to the "Cross-site user tracking" section. - Reported by Nettozahler in #3172525.
+Use the IP_FREEBIND socket option, if defined. This allows Privoxy to bind to not-yet assigned IP + addresses which is useful in failover environments. Patch by Sam Varshavchik.
Unblock and fast-redirect ".awin1.com/.*=http://" Reported by - Adam Piggott in #3170921.
+Allow to use extended host patterns and vanilla host patterns at the same time by prefixing extended + host patterns with "PCRE-HOST-PATTERN:". To enable this, configure with --enable-pcre-host-patterns. + Sponsored by: Robert Klemme
Block "b.collective-media.net/".
+Added "Cross-origin resource sharing" (CORS) support. This allows to access Privoxy's CGI interface via + JavaScript from another domain (white-listed with the new cors-allowed-origin directive). Based on a patch + by Nedzad Hrnjica. Sponsored by: Robert Klemme.
Widen the Debian popcon exception to "qa.debian.org/popcon". - Seen in Debian's 05_default_action.dpatch by Roland - Rosenfeld.
+Add SOCKS5 username/password support. Based on a patch by Sam, improved by Ivan Romanov. Closes + Patch#141 and solves TODO#105.
Block ".gemius.pl/" which only seems to be used for user - tracking. Reported by johnd16 in #3002731. Additional input from - Lee and movax.
+Bump the maximum number of action and filter files to 100 each. Sponsored by: Robert Klemme
Disable banners-by-size filters for '.thinkgeek.com/' The - filter only seems to catch pictures of the inventory.
+Fixed handling of filters with "split-large-forms 1" when using the CGI editor. Reported by withoutname + in #921.
Block requests for 'go.idmnet.bbelements.com/please/showit/' - Reported by kacperdominik in #3372959.
+Better detect a mismatch of connection details when figuring out whether or not a connection can be + reused.
Unblock adainitiative.org/
+Don't send a "Connection failure" message instead of the "DNS failure" message. Sponsored by: Robert + Klemme
Add a fast-redirects exception for - '.googleusercontent.com/.*=cache'
+Let LOG_LEVEL_REQUEST log all requests. Previously unencrypted requests were only logged with + LOG_LEVEL_REQUEST when they weren't crunched (in which case they were logged with LOG_LEVEL_CRUNCH). This + was documented behaviour, but logging all requests seems more useful.
Add a fast-redirects exception for - webcache.googleusercontent.com/
+Fixed locking around localtime() and gmtime().
Remove -prevent-compression from the fragile alias It's no - longer used anywhere by default and isn't known to break stuff - anyway.
+Removed OS/2 support. We haven't provided OS/2 packages in years, it complicated the code and it + depended on a fallback snprintf() implementation which is GPLv2 only.
Unblock http://adassier.wordpress.com/ and - http://adassier.files.wordpress.com/
+Remove the fallback snprintf() implementation Now that OS/2 support is gone we no longer need it.
Filter file improvements:
- -Let the yahoo filter hide '.ads'
+Fixed a bunch of format specifiers log messages.
Let the msn filter hide overlay ads for Facebook 'likes' in - search results.
+Added a missing apostrophe in the 'More Privoxy' menu.
Let the msn filter hide elements with the id 's_notf_div'. - They only seem to be used to advertise site 'enhancements'.
+Explicitly prevent use of FEATURE_CONNECTION_SHARING without FEATURE_CONNECTION_KEEP_ALIVE. It makes no + sense and does not compile anyway. Sponsored by: Robert Klemme
Let the js-events filter additionally disarm setInterval() - Suggested by dg1727 in #3423775.
+Fix build without FEATURE_CONNECTION_KEEP_ALIVE. Sponsored by: Robert Klemme
Documentation improvements:
- -Clarify the effect of compiling Privoxy with zlib support - Suggested by dg1727 in #3423782.
+Downgrade the 'Graceful termination requested' message to LOG_LEVEL_INFO as it isn't an error. Sponsored + by: Robert Klemme
Point out that the SourceForge messaging system works like a - blackhole and should thus not be used
+decompress_iob(): Downgrade the no-content message to LOG_LEVEL_RE_FILTER While at it, fix a typo in a + comment. Sponsored by: Robert Klemme
Mention some of the problems one can experience when not - explicitly configuring an IP addresses as listen address.
+Fixed a couple of cppcheck warnings.
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.
+Rename LOG_LEVEL_GPC to LOG_LEVEL_REQUEST. Only the shadow knows what "GPC" is supposed to stand + for.
Log message improvements:
- -If only the server connection is kept alive, do not pretent to - wait for a new client request.
+Remove SourceForge references in copyright headers.
Remove a superfluos log message in forget_connection()
+Upgrade a bunch of links to the homepage to https://.
In chat(), properly report missing server responses as such - instead of calling them empty
+Add 'no-brotli-accepted' filter which prevents the use of Brotli compression.
In forwarded_connect(), fix a log message nobody should ever - see
+Changed license for pcrs to GPLv2+ after getting the permission from Andreas. This allows to + redistribute Privoxy under the GPLv3 which is required when linking to future mbedTLS versions which are + expected to be licensed under the Apache 2.0 license only.
Fix a log message in socks5_connect(), a failed write - operation was logged as failed read operation
+Updated a bunch of tests that have to expect status code 403 now after r1.168/070e904afa5.
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.
+Lowercase the host name in the request line.
Do not claim to listen on a socket until we actually do. Patch - submitted by Petr Pisar #3354485
+Only set SOURCE_DATE_EPOCH if it's not already set so distributions can overwrite it through the + environment.
Prevent a duplicated LOG_LEVEL_CLF message when sending out - the "no-server-data" response
-Also log the client socket when dropping a connection.
-Include the destination host in the 'Request ... marked for - blocking. limit-connect{...} doesn't allow CONNECT ...' message - Patch submitted by Saperski in #3296250.
-Prevent a duplicated log message if none of the resolved IP - addresses were reachable
-In connect_to(), do not pretend to retry if - forwarded-connect-retries is zero or unset.
-When a specified user or group can't be found, put the name in - single-quotes when logging it.
-In rfc2553_connect_to(), explain getnameinfo() errors - differently.
-Remove a useless log message in chat()
-Documentation changes:
+When retrying to connect, also log the maximum number of - connection attempts
+Explain that Privoxy has to be distributed under the GPLv3 (or later) when linked with an MbedTLS + version that is licensed under the Apache 2.0 license.
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.
+Import the GNU GPLv3 and include it the user manual.
In a fatal error message in load_one_actions_file(), cover - both URL and TAG patterns
+Clarify FEATURE_FORCE_LOAD's description. It allows to bypass blocking not filtering and only does it if + blocks aren't enforced. Reported by: Robert Klemme
In pcrs_strerror(), properly report unknown positive error - code values as unknown. Previously they were handled like 0 (no - error).
+FAQ: Remove Zwiebelfreunde e.V. from the list of fiduciary sponsors As of 2021 they no longer handle + donations for foreign organisations due to lack of resources.
In compile_dynamic_pcrs_job_list(), also log the actual error - code as pcrs_strerror() doesn't handle all errors reported by - pcre
+FAQ: Remove an obsolete comment with a link to the long-gone PDF manual.
Don't bother trying to continue chatting if the client didn't - ask for it. Reduces log noise a bit.
+FAQ: Add a link to the TODO list.
Make two fatal error message in load_one_actions_file() more - descriptive
+FAQ: Change the sponsor amounts to USD slightly rounding the converted amounts up to get simple numbers. + Receiving USD is apparently easier for SPI and SPI is preferred by sponsors as they can send invoices.
In cgi_send_user_manual(), log when rejecting a file name due - to '/' or '..'
+Advertise the client-tags CGI page in the user manual.
In load_file(), log a message if opening a file failed The CGI - error message alone isn't too helpful.
+Stop advertising the show-version CGI page which no longer exists.
In connection_destination_matches(), improve two log messages - to help understand why the destinations don't match
+Add yet another reason why +prevent-compression may cause problems.
Rephrase a log message in serve(). Client request arrival - should be differentiated from closed client connections now.
+Don't claim that contributors need ssh. It's only needed for committers.
In serve(), log if a client connection isn't reused due to a - configuration file change.
+Replace obsolete CVS instructions with Git instructions.
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.
+Remove an obsolete comment
Miscellaneous Privoxy improvements:
- +Config file changes:
In get_last_url(), do not bother trying to decode URLs that do - not contain at least one '%' sign. It reduces the log noise and a - number of unnecessary memory allocations.
-If the --user argument user[.group] contains a dot, always - bail out if no group has been specified. Previously the intended, - but undocumented (and apparently untested), behaviour was to try - interpreting the whole argument as user name, but the detection - was flawed and checked for '0' isntead of '\0', thus merely - preventing group names beginning with a zero.
-Simplify the signal setup in main()
-Streamline socks5_connect() slightly
-In case of SOCKS5 failures, dump the socks response
-In socks5_connect(), require a complete socks response from - the server Previously we didn't care how much data the server - response contained as long as the first two bytes contained the - expected values. While at it, shrink the buffer size so we can't - read more than a whole socks response. This is required to - support Tor's optimistic data extension.
-In chat(), do not bother to generate a client request in case - of direct CONNECT requests
+Change the suggested default-server-timeout to 5 to match the suggested keep-alive-timeout. Otherwise + using the defaults would result in Privoxy reducing the default-server-timeout and logging an error + message. Sponsored by: Robert Klemme
Reduce server_last_modified()'s stack size
+Update the 'debug 1' description.
Shorten get_http_time() by using strftime()
+Add a missing 'client-specific-tag' directive.
Constify the known_http_methods pointers in - unknown_method()
+Comment out trusted-cgi-referer pointing to example.org.
Constify the time_formats pointers in parse_header_time()
-Action file improvements:
+Constify the formerly_valid_actions pointers in - action_used_to_be_valid()
+Block requests to /(.*/)?piwik\.php
In html_code_map[], use a numeric character reference instead - of ' which wasn't standardized before XHTML 1.0
+Block requests to .connectaserver.de/
Introduce a MAN_PAGE variable that defaults to privoxy.1. The - Debian package uses section 8 for the man page and this should - simplify the patch.
+Block requests to pixel.inforsea.com/
Deduplicate the INADDR_NONE definition for Solaris by moving - it to jbsockets.h
+Block requests to t.vi-serve.com/
In block_url(), ditch the obsolete workaround for ancient - Netscape versions that supposedly couldn't properly deal with - status code 403.
+Block requests to .ioam.de/
Remove a useless NULL pointer check in load_trustfile()
+Block requests to t.9gag.com/img.gif
Remove two useless NULL pointer checks in - load_one_re_filterfile().
+Block requests to .pixel.parsely.com/ as image
Change url_code_map[] from an array of pointers to an array of - arrays It removes an unnecessary layer of indirection and on - 64bit system reduces the size of the binary a bit.
+Block requests to pixel.wp.com/
Fix various typos. Fixes taken from Debian's 29_typos.dpatch - by Roland Rosenfeld.
+Disable fast-redirects for .librarything.com/
Add a dok-tidy GNUMakefile target to clean up the messy HTML - generated by the other dok targets.
+Disable fast-redirects for issue.freebsdfoundation.org/
GNUisms in the GNUMakefile have been removed.
+Disable fast-redirects for .twitter.com/.*origin=http
Change the HTTP version in static responses to 1.1
+Unblock belco24.de/
Synced config.sub and config.guess with upstream - 2011-11-11/386c7218162c145f5f9e1ff7f558a3fbb66c37c5.
+Add fast-redirects exception for .wikipedia.org/
Add a dedicated function to parse the values of toggles - Reduces duplicated code in load_config() and provides better - error handling. Invalid or missing toggle values are now a fatal - error instead of being silently ignored.
+Add fast-redirects exception for oss-fuzz.com/
Terminate HTML lines in static error messages with \n instead - of \r\n.
+Disable fast-redirects for .consensu.org/delivery/pixel\.php and block the requests as image instead
Simplify cgi_error_unknown() a bit.
+Unblock .adbinstaller.com/ Reported by lvm in #942.
In LogPutString(), don't bother looking at pszText when not - actually logging anything
+Unblock .adbshell.com Reported by lvm in #942.
Change ssplit()'s fourth parameter from int to size_t. Fixes a - clang complaint.
+Unblock .tagesschau.de/
Add a warning that the statistics currently can't be trusted. - Mention Privoxy-Log-Parser's --statistics option as an - alternative for the time being.
+Disable fast-redirects for collector.githubapp.com/ and block requests to it as image instead
In rfc2553_connect_to(), start setting cgi->error_message - on error
+Unblock 'ada*.'
Change the expected status code returned for http://p.p/die - depending on whether or not FEATURE_GRACEFUL_TERMINATION is - available.
+Add fast-redirects{} exception for sourcepoint.vice.com/
In cgi_die(), mark the client connection for closing. If the - client will fetch the style sheet through another connection it - gets the main thread out of the accept() state and should thus - trigger the actual shutdown.
+Unblock adaway.org/ Reported by DRS David Soft in AF#945.
Add a proper CGI message for cgi_die().
+Change two block reasons that previously were the same. Sponsored by: Robert Klemme
Fix an invalid free when compiled with - FEATURE_GRACEFUL_TERMINATION and shut down through - http://config.privoxy.org/die
+Added a +delay-response{} test.
Don't enforce a logical line length limit in - read_config_line()
+Updated the location of the development version of default.action.master.
Privoxy-Log-Parser:
+Slightly refactor server_last_modified() to remove useless - gmtime*() calls
+Added a --keep-date option to keep the date in highlighted messages.
In get_content_type(), also recognize '.jpeg' as JPEG - extension
+Highlight new log messages.
Add '.png' to the list of recognized file extenstions in - get_content_type()
+Make gather_loglevel_clf_stats() more tolerant. While at it, count all CLF messages as requests, even if + the request is invalid.
In block_url(), consistently use the block reason "Request - blocked by Privoxy" In two places the reason was "Request for - blocked URL" which hides the fact that the request got blocked by - Privoxy and isn't necessarly correct as the block may be due to - tags.
+Only show HTTP version distribution if at least one version has been detected.
In get_actions(), fix the "temporary" backwards compatibility - hack to accept block actions without reason. It also covered - other actions that should be rejected as invalid. Reported by - Billy Crook.
+Only show crunch statistics if crunches were detected.
In listen_loop(), reload the configuration files after - accepting a new connection instead of before. Previously the - first connection that arrived after a configuration change would - still be handled with the old configuration.
+Warn if the request counts differ.
In chat()'s receive-data loop, skip a client socket check if - the socket will be written to right away anyway. This can - increase the transfer speed for unfiltered content on fast - network connections.
+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.
The socket timeout is used for SOCKS negotiation as well.
+Align the client-HTTP-version distribution like other distributions
Don't keep the client connection alive if any configuration - file changed since the time the connection came in. This is - closer to Privoxy's behaviour before keep-alive support for - client connection has been added and also less confusing in - general.
+Bump version to 0.9.1
Treat all Content-Type header values containing the pattern - 'script' as a sign of text. Reported by pribog in #3134970.
+Include status code distribution in the stats.
configure:
- -Added a --disable-ipv6-support switch for platforms where - support is detected but doesn't actually work.
+Let the statistics include the size of the content Privoxy transferred excluding HTTP headers.
Do not check for the existence of strerror() and memmove() - twice
+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.
Remove a useless test for setpgrp(2). Privoxy doesn't need it - and it can cause problems when cross-compiling
+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
Rename the --disable-acl-files switch to --disable-acl-support - Since about 2001, ACL directives are specified in the standard - config file.
+Properly highlight the filter results message. Previously a brace got lost.
Update the URL of the 'Removing outdated PCRE version after - the next stable release' posting. The old URL stopped working - after one of SF's recent layout pessimizations. Reported by Han - Liu.
+Prefer the number of CLF lines to get the total number of requests as it works with older Privoxy + versions as well.
Privoxy-Regression-Test:
-Added --shuffle-tests option to increase the chances of - detection race conditions
-Added a --local-test-file option that allows to use - Privoxy-Regression-Test without Privoxy
-Added tests for missing socks4 and socks4a forwarders
-The --privoxy-address option now works with IPv6 addresses - containing brackets, too
+Turn curl's globbing mode off so we can allow more characters in URLs.
Perform limited sanity checks for parameters that are supposed - to have numerical values.
+Allow '[' and ']' in URLs.
Added a --sleep-time option to specify a number of seconds to - sleep between tests, defaults to 0.
+Include the action file when complaining about missing Sticky Actions.
Disable the range-requests tagger for tests that break if it's - enabled
+Fix a sentence in the documentation.
Log messages use the ISO 8601 date format %Y-%m-%d.
-Fix spelling in two error messages.
-In the --help output, include a list of supported tests and - their default levels.
+Bump version to 0.7.1
Privoxy-Log-Parser:
- +url-pattern-translator:
Perform limited sanity checks for parameters that are supposed - to have numerical values.
-Implement a --unbreak-lines-only option to try to revert MUA - breakage.
+Detect a couple of pattern prefixes case-insensitively. Sponsored by: Robert Klemme
Accept and highlight: Added header: Content-Encoding: - deflate
+Skip CLIENT-TAG patterns. Sponsored by: Robert Klemme
Accept and highlight: Compressed content from 29258 to 8630 - bytes.
+Skip patterns that have already been converted. It should now be safe to "convert" a file multiple + times. Sponsored by: Robert Klemme
Accept and highlight: Client request arrived in time on socket - 21.
-Highlight: Didn't receive data in time: a.fsdn.com:443
-Accept log messages with ISO 8601 time stamps, too
-uagen:
- -Bump generated Firefox version to 9.0
-Only randomize the release date if the new - --randomize-release-date option is enabled. Firefox versions - after 4 use a fixed date string without meaning.
+Add the new 'PCRE-HOST-PATTERN:' prefix. Sponsored by: Robert Klemme
A quick list of things to be aware of before upgrading from earlier - versions of Privoxy:
- +A quick list of things to be aware of before upgrading from earlier versions of Privoxy:
The recommended way to upgrade Privoxy is to backup your old configuration - files, install the new ones, verify that Privoxy is working correctly and finally merge - back your changes using diff and - maybe patch.
- -There are a number of new features in each Privoxy release and most of them have to be - explicitly enabled in the configuration files. Old configuration - files obviously don't do that and due to syntax changes using old - configuration files with a new The recommended way to upgrade Privoxy is to backup your old + configuration files, install the new ones, verify that Privoxy is working + correctly and finally merge back your changes using diff and maybe + patch.
+There are a number of new features in each Privoxy release and most of + them have to be explicitly enabled in the configuration files. Old configuration files obviously don't do + that and due to syntax changes using old configuration files with a new Privoxy isn't always possible anyway.
Note that some installers remove earlier versions completely, - including configuration files, therefore you should really save any - important configuration files!
-On the other hand, other installers don't overwrite existing - configuration files, thinking you will want to do that - yourself.
+Note that some installers remove earlier versions completely, including configuration files, therefore you + should really save any important configuration files!
standard.action has been merged into - the default.action file.
+On the other hand, other installers don't overwrite existing configuration files, thinking you will want + to do that yourself.
In the default configuration only fatal errors are logged now. - You can change that in the debug - section of the configuration file. You may also want to enable - more verbose logging until you verified that the new Privoxy version is working as expected.
+In the default configuration only fatal errors are logged now. You can change that in the debug section of the configuration file. You may also want to enable more verbose + logging until you verified that the new Privoxy version is working as + expected.
Three other config file settings are now off by default: - enable-remote-toggle, - enable-remote-http-toggle, - and enable-edit-actions. If you - use or want these, you will need to explicitly enable them, and be - aware of the security issues involved.
+Three other config file settings are now off by default: enable-remote-toggle, enable-remote-http-toggle, and enable-edit-actions. If you use or want these, you will need to + explicitly enable them, and be aware of the security issues involved.