Add upstream-tests scenario
authorFabian Keil <fk@fabiankeil.de>
Sun, 10 Jan 2021 15:18:17 +0000 (16:18 +0100)
committerFabian Keil <fk@fabiankeil.de>
Wed, 20 Mar 2024 11:38:39 +0000 (12:38 +0100)
Sponsored by: Privoxy project funds collected at SPI

tests/cts/upstream-tests/privoxy.conf [new file with mode: 0644]

diff --git a/tests/cts/upstream-tests/privoxy.conf b/tests/cts/upstream-tests/privoxy.conf
new file mode 100644 (file)
index 0000000..2bbef63
--- /dev/null
@@ -0,0 +1,25 @@
+listen-address 127.0.0.1:9119
+
+debug     1 # Log the destination for each request Privoxy let through. See also debug 1024.
+debug     2 # show each connection status
+debug     4 # show tagging-related messages
+debug     8 # show header parsing
+debug    32 # debug force feature
+debug    64 # debug regular expression filters
+debug   128 # debug redirects
+debug   256 # debug GIF de-animation
+debug   512 # Common Log Format
+debug  1024 # Log the destination for requests Privoxy didn't let through, and the reason why.
+debug  4096 # Startup banner and warnings.
+debug  8192 # Non-fatal errors
+
+#debug    16 # log all data written to the network
+#debug 32768 # log all data read from the network
+
+actionsfile ../../../default.action.master
+filterfile ../../../default.filter
+templdir ../../../templates
+
+keep-alive-timeout 5
+socket-timeout 5
+default-server-timeout 5