dns-over-https

Under multiport mode, plugins may need to know on which port was the request received/accepted. This information is currently not surfaced to plugins. For background also see abhinavsingh/proxy.py#535 (comment) thread

This http header is currently not implemented in Blocky DoH server.

Some famous DoH servers like those:

• AdGuard
• Quad9
• Quad101(Powered by https://github.com/m13253/dns-over-https)
• Google
• Applied Privacy DNS
• DNS.SB
• DNS Forge

They do return cache-control http header like the example mentioned in [RFC 8484 (DNS Queries over HTTPS (DoH))](https://datatracker.ietf.org/doc/

https://github.com/AdguardTeam/dnsproxy/blob/2f7a50c830677fd6fed48a071a5f8f4ff563c1a8/proxy/proxy_test.go#L751

https://github.com/AdguardTeam/dnsproxy/blob/2f7a50c830677fd6fed48a071a5f8f4ff563c1a8/proxy/proxy_test.go#L734

The golang comment says that Fatalf() must be called only from the goroutine running the Test function.

https://github.com/golang/go/blob/926994fd7cf65b2703552686965

Like ODoH via Cloudflare-WARP on Linux
or even supported Anycast Networks for example 🙏🏼🤞🏼

Using https://github.com/dollarshaveclub/cloudworker, unit tests should be implemented for all the HTTP routes in the worker.

For interactions, there should be unit tests to ensure that the verification middleware works as expected, and then unit tests should be provided for each command in the interactions app.