From: Remi Gacogne Date: Mon, 18 Sep 2023 11:47:44 +0000 (+0200) Subject: dnsdist: Document that h2o support is no longer built by default X-Git-Tag: rec-5.0.0-alpha2~59^2 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=refs%2Fpull%2F13274%2Fhead;p=thirdparty%2Fpdns.git dnsdist: Document that h2o support is no longer built by default --- diff --git a/pdns/dnsdistdist/docs/upgrade_guide.rst b/pdns/dnsdistdist/docs/upgrade_guide.rst index 9efab181f3..661370f6db 100644 --- a/pdns/dnsdistdist/docs/upgrade_guide.rst +++ b/pdns/dnsdistdist/docs/upgrade_guide.rst @@ -5,7 +5,7 @@ Upgrade Guide -------------- dnsdist now supports a new library for dealing with incoming DNS over HTTPS queries: ``nghttp2``. The previously used library, ``h2o``, can still be used -but is now deprecated and will be removed in the future, as it is unfortunately no longer maintained in a way that is suitable for use as a library +but is now deprecated, disabled by default (see ``--with-h2o`` to enable it back) and will be removed in the future, as it is unfortunately no longer maintained in a way that is suitable for use as a library (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