Smal fail changes.

[ACEx86]

Use the discussion to suggest things.

[ACEx86]

@jedisct1
Here TLS 1.2 old discussion 'https://github.com/DNSCrypt/dnscrypt-proxy/blob/299ebd24e6a0e94ee098c475e6e3eebf1a61f185/dnscrypt-proxy/serversInfo.go#L864C6-L864C24'
on older version when server used cipher suite was not the one configured the file dropped the request to GET:
Maybe on TLS failure don't drop the request's to get but retry until getting the wanted cipher suite?
On servers like cloudflare the same server may choose to use different cipher suites. With different IPs each time.
So on the old version proxy.xTransport.tlsCipherSuite = config.TLSCipherSuite and having something like only 49200 may have been a problem, something like this one: '#3012'.
You could have tried to get different advertisment instead on dropping or adding some secure cipher suites after failure or add the servers if it was a 'safe' one.

[ACEx86]

So with this approach isn't it a cool idea to maybe create a pool of connection to use for servers that act like this just to use the selected cipher suite?

[ACEx86]

@jedisct1
Is it a good idea for DoH to add a toml setting to force use GET or POST or BOTH?

[ACEx86]

@jedisct1
Here why we use add if when adding two elems toggether will fail the request or a request like GET anyway?
qs.Add("body_hash", hex.EncodeToString(h[:32]))
qs.Set("body_hash", hex.EncodeToString(h[:32]))
https://github.com/DNSCrypt/dnscrypt-proxy/blob/299ebd24e6a0e94ee098c475e6e3eebf1a61f185/dnscrypt-proxy/xtransport.go#L685C3-L685C50