[Privoxy-commits] [privoxy] 07/07: Regenerate curl-test-manifest-for-privoxy

User Git git at git.privoxy.org
Mon Apr 20 15:58:43 CEST 2026


This is an automated email from the git hooks/post-receive script.

git pushed a commit to branch master
in repository privoxy.

commit 801003cd1b8dbbf372b07f38cc834049c47e116a
Author: Fabian Keil <fk at fabiankeil.de>
AuthorDate: Mon Apr 13 09:28:27 2026 +0200

    Regenerate curl-test-manifest-for-privoxy
---
 tests/cts/curl-test-manifest-for-privoxy | 1 +
 1 file changed, 1 insertion(+)

diff --git a/tests/cts/curl-test-manifest-for-privoxy b/tests/cts/curl-test-manifest-for-privoxy
index a8b97a8a..3282cb74 100644
--- a/tests/cts/curl-test-manifest-for-privoxy
+++ b/tests/cts/curl-test-manifest-for-privoxy
@@ -48,6 +48,7 @@ test:1598: Expected to fail. Privoxy does not support chunk-encoded POST request
 test:16, 45, 63: Not supposed to work with Privoxy. Expected forwarding failure. Workaround probably possible.
 test:1665: Expected to fail. Trigger Privoxy's MS IIS 5 hack which the test does not expect.
 test:1671: Known to fail as curl adds a Proxy-Connection header to the JSON output which the test doesn't expect.
+test:1685: Known to fail as Privoxy converts a tab in a Cookie header to space.
 test:17: Not supposed to work with Privoxy. Invalid METHODs get rejected.
 test:187: Expected to fail. Test doesn't deal with Privoxy's error message in case of invalid URLs.
 test:19, 20: Not supposed to work with Privoxy. Tests behaviour with non-existing server and doesn't deal with error messages coming from a proxy.

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.


More information about the Privoxy-commits mailing list