[Privoxy-devel] Release date for Privoxy 4.2.0 stable

[Fabian Keil]

Roland Rosenfeld <roland at spinnaker.de> wrote on 2026-05-17 at 09:15:26:

> On Sun, 17 May 2026, Fabian Keil via Privoxy-devel wrote:
> 
> > Roland Rosenfeld <roland at spinnaker.de> wrote on 2026-05-16 at 10:01:06:
> > Thanks for checking. I admit that I did not actually test on GNU/Linux.
> > 
> > The tests that fail on your system have in common that they require
> > local IP addresses that aren't available on most systems by default
> > (for example 127.0.1.2 and 127.0.1.3).
> >
> > There's a helper script that is supposed to check if an IP address
> > is available. If it isn't, the test is supposed to be skipped.
> > 
> > I suspect that this isn't working on your system and it's conceivable
> > that this is something Linux-specific and not limited to your local
> > system.
> > 
> > Do you get an error message if you run "./tests/cts/bind-to-address.pl 127.0.1.3"?
> > 
> > Is 127.0.1.3 available on your system and is curl allowed to use
> > the address when testing?
> 
> This was a limitation in my local package filter (nftables), which
> only allowed 127.0.0.1 on loopback.  I extended this allow 127.0.0.0/8
> and the problems were reduced.
> Now acl-multiple-ip-addresses-specified-with-destination succeeds.

Great.

> acl-multiple-ip-addresses-specified-without-destination was reduced to
> two fails:
> 
> test 0004...[Request from client address from denied network range]
>  
> curl returned 52, when expecting 56
>  4: exit FAILED
> test 0005...[Request from client address from denied network range]
>  
> curl returned 52, when expecting 56
>  5: exit FAILED
> test 0006...[Request from client address from denied network range to destination that has an exception]
> ---d---e--- OK (6   out of 6  , remaining: 00:00, took 0.059s, duration: 00:01)
> TESTDONE: 6 tests were considered during 1 seconds.
> TESTDONE: 4 tests out of 6 reported OK: 66%
>  
> FAIL 4: 'Request from client address from denied network range' HTTP, HTTP GET
> FAIL 5: 'Request from client address from denied network range' HTTP, HTTP GET
>  
> TESTFAIL: These test cases failed: 4 5
> 
> I didn't understand what's going wrong here, yet.

Are you maybe not testing with a curl binary based on curl-8_20_0,
the current recommendation in tests/cts/README?

curl's exit code for the tested condition was recently changed
upstream and I updated the expected return codes to keep the tests
working with more recent curl versions.

For details see [0].

> acl-permit-access-with-exceptions fails on only one test:
> test 0004...[Request from client address from denied network range]
>  
>  4: data FAILED:
> Unprocessed headers:
> --- log/check-expected  2026-05-17 09:01:42.068380568 +0200
> +++ log/check-generated 2026-05-17 09:01:42.068380568 +0200
> @@ -1,11 +1,17 @@
> -HTTP/1.1 503 Connect failed[LF]
> -Content-Length: 44[LF]
> -Content-Type: text/html[LF]
> -Cache-Control: no-cache[LF]
> -X-Ignore-Header: Date[LF]
> +HTTP/1.1 404 Not Found[LF]
[...]
> Okay, this test expects, that no server is listening on 127.0.0.1:80,
> which isn't true on my development machine.  If I stop apache2, the
> test succeeds :-)

Looks like the test is flawed. I will look into it.

Fabian

[0] <https://www.privoxy.org/gitweb/?p=privoxy.git;a=commitdiff;h=cd39f62455ce4808ae7b89bb82f08765c42ac8dd>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.privoxy.org/pipermail/privoxy-devel/attachments/20260519/e92f99cf/attachment.bin>