quic-go has made breaking changes since v0.35.0, includes implementing
`CloseIdleConnections`.
Now, the local listener UDPConn are reused, and don't pile up. But,
1 instance (IPv4/IPv6) persists for each connected server.
* 'master' of github.com:DNSCrypt/dnscrypt-proxy:
Bump softprops/action-gh-release (#2357)
Bump actions/setup-go from 3 to 4 (#2354)
Update deps
Format
Better description for ignore_system_dns
Move booleans together for alignment, avoid unneeded format string
Try dnscrypt-proxy to resolve configured hosts when ignore_system_dns (#2204)
Downgrade to TLS 1.2 if an 1.3-incompatible cipher suite is set
* Adding the ability to do TLS client authentication for DoH
* whitespace nit
* Check for server specific creds before wildcard
* small comma ok idiom change
Resolvers such as Cloudflare always add padding to DoH responses
Resolvers such as Google only do if the question had dumb padding
Resolvers such as Cisco blindly return a copy of the question's padding
Some resolvers don't return any padding no matter what's in the question
Finally, other resolvers return FORMERR
This is a mess. A bad design inherited from DoT, that didn't fix
anything from Unbound's original experiment.
Also, padding with zeros as recommended is a bad idea. When using
GET, escaping makes the actual padding size 3 times as big as needed.
This mechanism is horrible, slow (requires re-unpacking and re-packing
the query), should be done at transport layer and not at content layer, and
of course, it is incompatible with some resolvers.
However, in spite of https://go-review.googlesource.com/c/go/+/114316/2/src/net/http/transfer.go ,
we may still end up sending the header and the content in distinct packets.
So, use that horror for POST queries only. For GET, this is not needed.
Frank Denis
YX Hao
Deltadroid
Ian Bashford
Christopher Wood
Frank Denis
Kevin O'Sullivan