From git at git.privoxy.org Fri Aug 8 14:19:56 2025 From: git at git.privoxy.org (User Git) Date: Fri, 08 Aug 2025 14:19:56 +0200 Subject: [Privoxy-commits] [privoxy] branch master updated (7daede88 -> 863f2b68) Message-ID: <175465559618.29650.8076966353800970671@privoxy-git> This is an automated email from the git hooks/post-receive script. git pushed a change to branch master in repository privoxy. from 7daede88 privoxy-log-parser: Highlight 'Giving up draining socket 35.' new 2b7c7e7e Disable deanimate-gifs for .githubusercontent.com/ new ca7732f0 Unblock .crates.io/ new f2e6db75 tests/cts/gen-skip-reasons.pl: Skip a bunch more tests that fail when using more recent upstream sources new 7a6c04ce Regenerate curl-test-manifest-for-privoxy new cf6f097e tests: Increase the socket-timeout for the upstream tests to 6 seconds new 863f2b68 tests/cts/gzip-compression/data/test13: Fix repetitive sequence by adding a missing % The 6 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: default.action.master | 4 ++++ tests/cts/curl-test-manifest-for-privoxy | 14 +++++++++++++- tests/cts/gen-skip-reasons.pl | 27 +++++++++++++++++++++++++-- tests/cts/gzip-compression/data/test13 | 2 +- tests/cts/upstream-tests/privoxy.conf | 2 +- 5 files changed, 44 insertions(+), 5 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Fri Aug 8 14:19:59 2025 From: git at git.privoxy.org (User Git) Date: Fri, 08 Aug 2025 14:19:59 +0200 Subject: [Privoxy-commits] [privoxy] 03/06: tests/cts/gen-skip-reasons.pl: Skip a bunch more tests that fail when using more recent upstream sources In-Reply-To: <175465559618.29650.8076966353800970671@privoxy-git> References: <175465559618.29650.8076966353800970671@privoxy-git> Message-ID: <20250808121957.7E64610E8E@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit f2e6db756da6dcf9120b7466957543597cccbb36 Author: Fabian Keil AuthorDate: Fri Aug 8 11:50:20 2025 +0200 tests/cts/gen-skip-reasons.pl: Skip a bunch more tests that fail when using more recent upstream sources --- tests/cts/gen-skip-reasons.pl | 27 +++++++++++++++++++++++++-- 1 file changed, 25 insertions(+), 2 deletions(-) diff --git a/tests/cts/gen-skip-reasons.pl b/tests/cts/gen-skip-reasons.pl index bd448d7b..da79f1f1 100755 --- a/tests/cts/gen-skip-reasons.pl +++ b/tests/cts/gen-skip-reasons.pl @@ -30,7 +30,9 @@ sub main() { for my $testnum (1..3500) { my $why; - if ($testnum eq 8) { + if ($testnum eq 2) { + $why = "Expected to fail. Missing space after status code that gets added by Privoxy."; + } elsif ($testnum eq 8) { $why = "Expected to fail. Tab in cookie that Privoxy converts to a space which the test does not expect."; } elsif ($testnum eq 16 or $testnum eq 45 or @@ -66,7 +68,7 @@ sub main() { $why = "Known to fail. Uses chunk trailers which Privoxy currently doesn't support."; } elsif ($testnum eq 309) { $why = "Known to fail. Uses https and test does not expect the 'Connection established' response from Privoxy"; - } elsif ($testnum eq 339 or $testnum eq 347 or $testnum eq 1591) { + } elsif ($testnum eq 339 or $testnum eq 347 or $testnum eq 1482 or $testnum eq 1483 or $testnum eq 1591) { $why = "Chunked transfer with trailers which Privoxy does not understand. Needs investigating."; } elsif ($testnum eq 389) { $why = "Known to fail depending on the DNS resolver on the system as Privoxy does not implement RFC6761 internally."; @@ -86,6 +88,12 @@ sub main() { $why = "Known to fail. Control code in Content-Length header."; } elsif ($testnum eq 435) { $why = "Expected to fail. Uses %{remote_port} and expects the port of the server and not the one from Privoxy."; + } elsif ($testnum eq 439) { + $why = "Expected to fail. Privoxy adds a 'Connection established' response the test does not expect."; + } elsif ($testnum eq 461) { + $why = "Expected to fail. Privoxy adds a 'Host' header."; + } elsif ($testnum eq 471 or $testnum eq 1704) { + $why = "Expected to fail. Uses HTTP/2 which Privoxy does not support."; } elsif ($testnum eq 507) { $why = "Expected to fail. DNS failures cause a Privoxy error message the test doesn't handle."; } elsif ($testnum eq 501) { @@ -101,6 +109,8 @@ sub main() { $why = "Expected to fail. POST request doesn't make it to the server. Needs investigating."; } elsif ($testnum eq 655) { $why = "Expected to fail. Uses tool. Failure reason not yet analyzed"; + } elsif ($testnum eq 696) { + $why = "Expected to fail. Test uses tool that does not support proxies."; } elsif ($testnum eq 970 or $testnum eq 972) { $why = "Expected to fail. Privoxy adds a Proxy-Connection header which results in a modified num_headers value in the JSON output"; } elsif ($testnum eq 1074) { @@ -120,6 +130,10 @@ sub main() { $why = "Expected to fail. Privoxy unfolds the folded headers which the test does not expect."; } elsif ($testnum eq 1433) { $why = "Expected to fail. Privoxy will enforce a valid HTTP version number"; + } elsif ($testnum eq 1479) { + $why = "Expected to fail. Uses HTTP/0.9 response."; + } elsif ($testnum eq 1480) { + $why = "Expected to fail. Uses HTTP Continue response but no final response."; } elsif ($testnum eq 1506 or $testnum eq 1510) { $why = "Expected to fail when using a proxy. Hardcoded addresses in expected output."; } elsif ($testnum eq 1156) { @@ -128,12 +142,18 @@ sub main() { $why = "Expected to fail as Privoxy does not support HTTP/0.9."; } elsif ($testnum eq 1292) { $why = "Expected to fail as Privoxy replaces the empty Host header."; + } elsif ($testnum eq 1499) { + $why = "Expected to fail. Privoxy does not support chunked trailers."; } elsif ($testnum eq 1533) { $why = "Sends an invalid method. Needs investigating."; + } elsif ($testnum eq 1542) { + $why = "Expected to fail. Expects HTTPPORT in logs which gets replaced by Privoxy's listening port."; } elsif ($testnum eq 1543) { $why = "Expected to fail as the URL contains spaces. XXX: Looks like a curl bug that should be investigated."; } elsif ($testnum eq 1556) { $why = "Known to fail. Body value changes from 100008 to 100009. Needs investigating."; + } elsif ($testnum eq 1598) { + $why = "Expected to fail. Privoxy does not support chunk-encoded POST requests with trailers."; } elsif ($testnum eq 1671) { $why = "Known to fail as curl adds a Proxy-Connection header to the JSON output which the test doesn't expect."; } elsif ($testnum eq 1915) { @@ -150,6 +170,8 @@ sub main() { $why = "Test 96 is incomplete"; } elsif ($testnum eq 1901 or $testnum eq 1902 or $testnum eq 1903) { $why = "Known to fail due to different response orders."; + } elsif ($testnum eq 1960) { + $why = "Known to fail. Test does not expect proxy request."; } elsif ($testnum eq 2100) { $why = "Known to fail. Use DNS-over-HTTP."; } elsif ($testnum eq 3014 or $testnum eq 3015) { @@ -186,6 +208,7 @@ sub main() { printf("keyword:%s: Tests with keyword '%s' aren't expected to work with Privoxy running in a jail without IPv6 connectivity.\n", 'IPv6', 'IPv6'); printf("keyword:%s: Tests with keyword '%s' don't work with Privoxy as they use the OPTIONS method which is currently not properly supported (TODO #186).\n", '--request-target', '--request-target'); + printf("keyword:%s: Tests with keyword '%s' don't work with Privoxy.\n", 'DOH', 'DOH'); printf("keyword:%s: Tests with keyword '%s' obviously should be skipped. Check the full keyword for details.\n", 'skip', 'skip'); -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Fri Aug 8 14:19:58 2025 From: git at git.privoxy.org (User Git) Date: Fri, 08 Aug 2025 14:19:58 +0200 Subject: [Privoxy-commits] [privoxy] 02/06: Unblock .crates.io/ In-Reply-To: <175465559618.29650.8076966353800970671@privoxy-git> References: <175465559618.29650.8076966353800970671@privoxy-git> Message-ID: <20250808121957.448ED10E8D@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit ca7732f0ebcf2afa5821984f0e4df8df7c643f9e Author: Fabian Keil AuthorDate: Wed Jul 23 05:29:22 2025 +0200 Unblock .crates.io/ --- default.action.master | 2 ++ 1 file changed, 2 insertions(+) diff --git a/default.action.master b/default.action.master index acf38e39..6ddd6018 100644 --- a/default.action.master +++ b/default.action.master @@ -2067,6 +2067,8 @@ pinkstinks.de/ .eff.org/ # URL = https://www.datenschmutz.de/banner-square.png .datenschmutz.de/ +# URL = https://index.crates.io/ad/le/adler +.crates.io/ ############################################################################# -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Fri Aug 8 14:19:57 2025 From: git at git.privoxy.org (User Git) Date: Fri, 08 Aug 2025 14:19:57 +0200 Subject: [Privoxy-commits] [privoxy] 01/06: Disable deanimate-gifs for .githubusercontent.com/ In-Reply-To: <175465559618.29650.8076966353800970671@privoxy-git> References: <175465559618.29650.8076966353800970671@privoxy-git> Message-ID: <20250808121956.F283C10E1B@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit 2b7c7e7e561f8c8d38e49ac77cff1e1d9b1ab2bd Author: Fabian Keil AuthorDate: Tue Jul 22 20:48:14 2025 +0200 Disable deanimate-gifs for .githubusercontent.com/ --- default.action.master | 2 ++ 1 file changed, 2 insertions(+) diff --git a/default.action.master b/default.action.master index c63cf7f8..acf38e39 100644 --- a/default.action.master +++ b/default.action.master @@ -2543,6 +2543,8 @@ schneegans.de/sv/\?url=referer .rubberslug.com #MASTER# REMARKS: Actionsfile feedback item #2040467, allow animated gifs from wikipedia.org .wikipedia.org/ +# URL = https://raw.githubusercontent.com/asomers/ztop/master/doc/demo.gif +.githubusercontent.com/ #---------------------------------------------------------------------------- # The "site-specifics" filter has special cures for problems found here: -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Fri Aug 8 14:20:00 2025 From: git at git.privoxy.org (User Git) Date: Fri, 08 Aug 2025 14:20:00 +0200 Subject: [Privoxy-commits] [privoxy] 04/06: Regenerate curl-test-manifest-for-privoxy In-Reply-To: <175465559618.29650.8076966353800970671@privoxy-git> References: <175465559618.29650.8076966353800970671@privoxy-git> Message-ID: <20250808121958.05F5910E1F@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit 7a6c04cefda66a38fe21d09ae1e0ac360bf840f1 Author: Fabian Keil AuthorDate: Fri Aug 8 13:06:50 2025 +0200 Regenerate curl-test-manifest-for-privoxy --- tests/cts/curl-test-manifest-for-privoxy | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/tests/cts/curl-test-manifest-for-privoxy b/tests/cts/curl-test-manifest-for-privoxy index a8e920fe..35d78400 100644 --- a/tests/cts/curl-test-manifest-for-privoxy +++ b/tests/cts/curl-test-manifest-for-privoxy @@ -3,6 +3,7 @@ keyword:--request-target: Tests with keyword '--request-target' don't work with keyword:--resolve: Tests with keyword '--resolve' currently don't work with Privoxy as they need additional runtests.pl changes. keyword:curl-config: Tests with keyword 'curl-config' do not reach the proxy. Or do they? keyword:CURLOPT_RESOLVE: Tests with keyword 'CURLOPT_RESOLVE' currently don't work with Privoxy as they need additional runtests.pl changes. +keyword:DOH: Tests with keyword 'DOH' don't work with Privoxy. keyword:FAILURE: Tests with keyword 'FAILURE' do not reach the proxy. Or do they? keyword:FILE: Protocol FILE is not supported by Privoxy. keyword:FTP: Protocol FTP is not supported by Privoxy. @@ -33,12 +34,17 @@ test:129: Invalid HTTP version. Privoxy downgrades it to 1.1. test:1292: Expected to fail as Privoxy replaces the empty Host header. test:1310: Known to fail. NTLM-related. Cause not properly diagnosed yet. Privoxy's behaviour seems reasonable. test:1433: Expected to fail. Privoxy will enforce a valid HTTP version number +test:1479: Expected to fail. Uses HTTP/0.9 response. +test:1480: Expected to fail. Uses HTTP Continue response but no final response. +test:1499: Expected to fail. Privoxy does not support chunked trailers. test:1506, 1510: Expected to fail when using a proxy. Hardcoded addresses in expected output. test:1533: Sends an invalid method. Needs investigating. +test:1542: Expected to fail. Expects HTTPPORT in logs which gets replaced by Privoxy's listening port. test:1543: Expected to fail as the URL contains spaces. XXX: Looks like a curl bug that should be investigated. test:155: Known to fail. Not yet analyzed. test:1556: Known to fail. Body value changes from 100008 to 100009. Needs investigating. test:158, 246, 565, 579: Known to fail. Not properly analyzed. Looks like Privoxy's continue hack is insufficient. +test:1598: Expected to fail. Privoxy does not support chunk-encoded POST requests with trailers. test:16, 45, 63: Not supposed to work with Privoxy. Expected forwarding failure. Workaround probably possible. test:1671: Known to fail as curl adds a Proxy-Connection header to the JSON output which the test doesn't expect. test:17: Not supposed to work with Privoxy. Invalid METHODs get rejected. @@ -47,6 +53,8 @@ test:19, 20: Not supposed to work with Privoxy. Tests behaviour with non-existin test:1901, 1902, 1903: Known to fail due to different response orders. test:1915: Known to fail. Uses tool that doesn't expect a proxy. test:1933: Known to fail. Modified signature in Authorization header. Needs investigating +test:1960: Known to fail. Test does not expect proxy request. +test:2: Expected to fail. Missing space after status code that gets added by Privoxy. test:2032, 2033: Known to fail due to a limitation of the test which doesn't properly deal with interleaved output from two parallel connections test:2049, 2052, 2053, 2054: Uses --connect-to. Need investigating. test:207: Expected to fail. Test doesn't handle Privoxy's error message. Privoxy doesn't behave correctly, though. @@ -59,12 +67,15 @@ test:30, 37, 66, 1079: Expected to fail with Privoxy. In case of missing server test:3014, 3015: Known to fail. Curl adds a Proxy-Connection header while test expect a certain number of headers. test:309: Known to fail. Uses https and test does not expect the 'Connection established' response from Privoxy test:31, 1105, 1160: Expected to fail. Privoxy normalizes white-space in a cookie. -test:339, 347, 1591: Chunked transfer with trailers which Privoxy does not understand. Needs investigating. +test:339, 347, 1482, 1483, 1591: Chunked transfer with trailers which Privoxy does not understand. Needs investigating. test:389: Known to fail depending on the DNS resolver on the system as Privoxy does not implement RFC6761 internally. test:412, 413: Known to fail as curl is tunneling the request even though it's vanilla HTTP. test:415: Known to fail. Control code in Content-Length header. test:435: Expected to fail. Uses %%{remote_port} and expects the port of the server and not the one from Privoxy. +test:439: Expected to fail. Privoxy adds a 'Connection established' response the test does not expect. test:46: Invalid URL and use of --resolv. +test:461: Expected to fail. Privoxy adds a 'Host' header. +test:471, 1704: Expected to fail. Uses HTTP/2 which Privoxy does not support. test:501: Not relevant for a proxy. test:507: Expected to fail. DNS failures cause a Privoxy error message the test doesn't handle. test:530, 584: Known to fail. Test server expects pipelined requests and doesn't respond otherwise. @@ -73,6 +84,7 @@ test:581: Expected to fail. Privoxy removes second Content-Type header. test:587, 644: Expected to fail. POST request doesn't make it to the server. Needs investigating. test:59: Invalid URL gets rejected by Privoxy which the test can't handle. test:655: Expected to fail. Uses tool. Failure reason not yet analyzed +test:696: Expected to fail. Test uses tool that does not support proxies. test:8: Expected to fail. Tab in cookie that Privoxy converts to a space which the test does not expect. test:96: Test 96 is incomplete test:970, 972: Expected to fail. Privoxy adds a Proxy-Connection header which results in a modified num_headers value in the JSON output -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Fri Aug 8 14:20:01 2025 From: git at git.privoxy.org (User Git) Date: Fri, 08 Aug 2025 14:20:01 +0200 Subject: [Privoxy-commits] [privoxy] 05/06: tests: Increase the socket-timeout for the upstream tests to 6 seconds In-Reply-To: <175465559618.29650.8076966353800970671@privoxy-git> References: <175465559618.29650.8076966353800970671@privoxy-git> Message-ID: <20250808121958.57A1110E21@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit cf6f097e99b2c61356119f7cc31ac25fcb2d465a Author: Fabian Keil AuthorDate: Fri Aug 8 12:20:54 2025 +0200 tests: Increase the socket-timeout for the upstream tests to 6 seconds ... so the upstream test 671 works which uses a pause of 5 seconds. --- tests/cts/upstream-tests/privoxy.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/cts/upstream-tests/privoxy.conf b/tests/cts/upstream-tests/privoxy.conf index 2bbef63c..7ce8aa56 100644 --- a/tests/cts/upstream-tests/privoxy.conf +++ b/tests/cts/upstream-tests/privoxy.conf @@ -21,5 +21,5 @@ filterfile ../../../default.filter templdir ../../../templates keep-alive-timeout 5 -socket-timeout 5 +socket-timeout 6 default-server-timeout 5 -- To stop receiving notification emails like this one, please contact the administrator of this repository. From git at git.privoxy.org Fri Aug 8 14:20:02 2025 From: git at git.privoxy.org (User Git) Date: Fri, 08 Aug 2025 14:20:02 +0200 Subject: [Privoxy-commits] [privoxy] 06/06: tests/cts/gzip-compression/data/test13: Fix repetitive sequence by adding a missing % In-Reply-To: <175465559618.29650.8076966353800970671@privoxy-git> References: <175465559618.29650.8076966353800970671@privoxy-git> Message-ID: <20250808121958.A311F10E8F@git.privoxy.org> This is an automated email from the git hooks/post-receive script. git pushed a commit to branch master in repository privoxy. commit 863f2b68a66dfb770dd491853dac5b761a82f473 Author: Fabian Keil AuthorDate: Wed Aug 6 15:37:41 2025 +0200 tests/cts/gzip-compression/data/test13: Fix repetitive sequence by adding a missing % --- tests/cts/gzip-compression/data/test13 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/cts/gzip-compression/data/test13 b/tests/cts/gzip-compression/data/test13 index 87f5a0af..cefbf277 100644 --- a/tests/cts/gzip-compression/data/test13 +++ b/tests/cts/gzip-compression/data/test13 @@ -16,7 +16,7 @@ Content-Type: text/html Content-Encoding: gzip X-Control: swsclose -%hex[%1f%8b%08%0C%a2%c1%12%60%00%00%00%01]hex%%repeat[256 x A]%hex[%0A%61%66%61%73%65%6c%00%73%ca%49%4c%4b%2c%4e%cd%51%48%c9%4c%55%48%49%e4%0a%ce%cf%4d%55%c8%cd%2f%02%71%4a%12%15%32%52%8b%52%b9%00%62%37%9b%0c%24%00%00%00%0a]hex% +%hex[%1f%8b%08%0C%a2%c1%12%60%00%00%00%01]hex%%repeat[256 x A]%%hex[%0A%61%66%61%73%65%6c%00%73%ca%49%4c%4b%2c%4e%cd%51%48%c9%4c%55%48%49%e4%0a%ce%cf%4d%55%c8%cd%2f%02%71%4a%12%15%32%52%8b%52%b9%00%62%37%9b%0c%24%00%00%00%0a]hex% -- To stop receiving notification emails like this one, please contact the administrator of this repository.