Fixes
-
DoH resolvers that require HTTP/2 are no longer reported as failing. RFC 8484 section 5.2 lets a DNS-over-HTTPS server insist on HTTP/2, and some do - FDN's
ns0.fdn.frandns1.fdn.franswer an HTTP/1.1 request with400 Bad Requestand a note saying HTTP/2 is required. The benchmark sent HTTP/1.1, so those resolvers came back as errors and looked blocked or broken even though they work perfectly in a browser or any normal DoH client.DoH queries now ask for HTTP/2 and fall back to HTTP/1.1 for servers that only speak it, so strict RFC 8484 endpoints are measured correctly and resolvers that never supported HTTP/2 are unaffected.
Thanks to the tester who reported FDN's DoH showing as blocked while it resolved fine when tested by hand - that report was correct, and the fault was on our side.
Assets
- Windows installer:
DNS-Hop-Setup-v2.4.4.exe - Windows portable:
DNS-Hop-Portable-v2.4.4.zip - Linux:
DNS-Hop-AppImage-v2.4.4-x86_64.AppImage(with.sha256)