[Privoxy-devel] Test failures delaying the 4.0.0 release (was: Releasing 3.0.35 or 4.0?)

[Roland Rosenfeld]

Hi Fabian!

On Sun, 12 Jan 2025, Fabian Keil via Privoxy-devel wrote:

> On my system acl-destination-denied is now the only failing scenario.

And what's about acl-ip-address-denied, does this work for you without
changing the return value from 56 to 52?

> > I'm currently running "make test" on curl (without privoxy) to check,
> > whether test389 works as expected (I don't understand why
> > curlmachine.locahost should ever work).

> On my systems hostnames ending in .localhost resolve to 127.0.0.1 and ::1.

On my system this isn't the case.  I first had to install
systemd-resolved and point DNS to 127.0.0.53 instead of using the
locally installed bind on 127.0.0.1.

If I activate this change, test389 runs okay in privoxy
upstream-tests, otherwise it fails.

But it's irritating, that the curl testsuite (without privoxy)
succeeds in test389 without the change.  Maybe curl has some resolver
library included, that resolves curlmachine.localhost to 127.0.0.1,
whithout asking the resolver defined in /etc/resolv.conf?
Just tried out, this seems to be the case.
When I run
 curl http://curlmachine.localhost
there is no request in the bind log ("host curlmachine.localhost"
shows one).

Surprisingly also
 ping curlmachine.localhost
works (and pings ::1) and doesn't log in bind log.
So there seems to be some voodoo in DNS resolution that works for curl
and ping but not for privoxy...

Anyway, I can work around this issue by changing my resolver to
resolve curlmachine.localhost, but the difference of the behavior of
curl and privoxy is strange.

Greetings
Roland
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.privoxy.org/pipermail/privoxy-devel/attachments/20250112/b9a7174d/attachment.bin>