From: Remi Gacogne Date: Mon, 14 Aug 2023 09:21:39 +0000 (+0200) Subject: dnsdist: Fix a typo (HTTP/1->2) in the DoH doc, as reported by Frank Louwers (thanks!) X-Git-Tag: rec-5.0.0-alpha1~19^2~4 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=7191b41a22b799e20970a3f44ef15209707b2f51;p=thirdparty%2Fpdns.git dnsdist: Fix a typo (HTTP/1->2) in the DoH doc, as reported by Frank Louwers (thanks!) --- diff --git a/pdns/dnsdistdist/docs/guides/dns-over-https.rst b/pdns/dnsdistdist/docs/guides/dns-over-https.rst index 226dbc49fa..6f4e5d16b6 100644 --- a/pdns/dnsdistdist/docs/guides/dns-over-https.rst +++ b/pdns/dnsdistdist/docs/guides/dns-over-https.rst @@ -61,7 +61,7 @@ dnsdist initially relied on the ``h2o`` library to support incoming DNS over HTT preferred library for incoming DoH support, because ``h2o`` has unfortunately really never been maintained in a way that is suitable for use as a library (see https://github.com/h2o/h2o/issues/3230). While we took great care to make the migration as painless as possible, ``h2o`` supported HTTP/1 while ``nghttp2`` does not. This is not an issue for actual DNS over HTTPS clients that support HTTP/2, but might be one in setups running dnsdist behind a reverse-proxy that -does not support HTTP/1, like nginx. We do not plan on implementing HTTP/1, and recommend using HTTP/2 between the reverse-proxy and dnsdist for performance reasons. +does not support HTTP/2, like nginx. We do not plan on implementing HTTP/1, and recommend using HTTP/2 between the reverse-proxy and dnsdist for performance reasons. For nginx in particular, a possible work-around is to use the `grpc_pass `_ directive as suggested in their `bug tracker `_. Internal design