From: Remi Gacogne Date: Fri, 21 Jul 2023 17:19:15 +0000 (+0200) Subject: dnsdist: Fix spelling issues X-Git-Tag: rec-5.0.0-alpha1~19^2~7 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=24edf3f5b9d2ae3a21b74ace6594ce9910a3837e;p=thirdparty%2Fpdns.git dnsdist: Fix spelling issues --- diff --git a/.github/actions/spell-check/expect.txt b/.github/actions/spell-check/expect.txt index b451e038dc..052d5d20ef 100644 --- a/.github/actions/spell-check/expect.txt +++ b/.github/actions/spell-check/expect.txt @@ -511,6 +511,7 @@ gpgsqlbackend gprof gpsqlbackend grepq +grpc GSQ gsql gsqlite diff --git a/pdns/dnsdistdist/docs/guides/dns-over-https.rst b/pdns/dnsdistdist/docs/guides/dns-over-https.rst index 1367a99c7c..226dbc49fa 100644 --- a/pdns/dnsdistdist/docs/guides/dns-over-https.rst +++ b/pdns/dnsdistdist/docs/guides/dns-over-https.rst @@ -62,7 +62,7 @@ preferred library for incoming DoH support, because ``h2o`` has unfortunately re (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. -For nginx in particular, a possible work-around is to use the `gprc_pass `_ directive as suggested in their `bugtracker `_. +For nginx in particular, a possible work-around is to use the `grpc_pass `_ directive as suggested in their `bug tracker `_. Internal design ^^^^^^^^^^^^^^^ diff --git a/pdns/dnsdistdist/docs/upgrade_guide.rst b/pdns/dnsdistdist/docs/upgrade_guide.rst index 7f58f3270e..575dd56fae 100644 --- a/pdns/dnsdistdist/docs/upgrade_guide.rst +++ b/pdns/dnsdistdist/docs/upgrade_guide.rst @@ -9,7 +9,7 @@ but is now deprecated and will be removed in the future, as it is unfortunately (see https://github.com/h2o/h2o/issues/3230). See the ``library`` parameter on the :func:`addDOHLocal` directive for more information on how to select the library used when dnsdist is built with support for both ``h2o`` and ``nghttp2``. The default is now ``nghttp2`` whenever possible. Note that ``nghttp2`` only supports HTTP/2, and not HTTP/1, while ``h2o`` supported both. 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. See :doc:`guides/dns-over-https` for some work-arounds. +support HTTP/2, but might be one in setups running dnsdist behind a reverse-proxy that does not support HTTP/1. See :doc:`guides/dns-over-https` for some work-around. 1.7.x to 1.8.0 --------------