Skip to content

doh2: restrict/configure URI path endpoints

Current doh2 implementation answers HTTP/2 requests on any URI path, although only /dns-query is documented (and supported). This path seems to be the most widespread among implementations.

Since our legacy DoH supported /doh, I'd also keep that path for the new implementation.

However, it'd probably be better to not answer to any random path, such as /odksjafo.

It might be worth considering whether making these endpoints user-configurable would be useful.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information