mirror of
https://github.com/MariaDB/server.git
synced 2026-10-23 18:49:29 +03:00
a349bb8501
The tests test_proxy_header_connect_errors_reset() and test_proxy_header_host_denied_not_counted() rely on their client IPs (192.0.2.x test IPs, per RFC 5737) failing reverse DNS lookup permanently, which is what a real, working resolver reports for them. Linux's resolver isn't so RFC-compliant, when it has no route to any nameserver at all: it reports EAI_AGAIN (temporary) instead, which is deliberately excluded from connect-error accounting to avoid blocking hosts during a DNS outage. That silently defeats the max_connect_errors check these tests exercise. Fix by forcing the deterministic "permanent failure" outcome via the existing getnameinfo_error_noname debug instrumentation, same as its sibling tests. Debug-only, like those siblings, since the workaround needs DBUG_EXECUTE_IF. Assisted-By: Claude Sonnet 5 <noreply@anthropic.com>