From: Krombel Date: Tue, 19 Nov 2019 14:56:39 +0000 (+0100) Subject: dnsdist: Fix formatting on DoH guide X-Git-Tag: auth-4.3.0-alpha1~35^2~1 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=1273099f9a0b3de1625cc8f5a3338e7951388d01;p=thirdparty%2Fpdns.git dnsdist: Fix formatting on DoH guide --- diff --git a/pdns/dnsdistdist/docs/guides/dns-over-https.rst b/pdns/dnsdistdist/docs/guides/dns-over-https.rst index 919e718200..2cf6fadbb8 100644 --- a/pdns/dnsdistdist/docs/guides/dns-over-https.rst +++ b/pdns/dnsdistdist/docs/guides/dns-over-https.rst @@ -23,11 +23,11 @@ DoH. If you want your DoH server to handle the call to :func:`addDOHLocal`. It is optional and defaults to ``/``, the root of your HTTP site. The fifth parameter, if present, indicates various options. For -instance, you use it to indicate custom HTTP headers. An example is: +instance, you use it to indicate custom HTTP headers. An example is:: addDOHLocal('2001:db8:1:f00::1', '/etc/ssl/certs/example.com.pem', '/etc/ssl/private/example.com.key', "/dns", {customResponseHeaders={["x-foo"]="bar"}} -A more complicated (and more realistic) example is when you want to indicate metainformation about the server, such as the stated policy (privacy statement and so on). We use the link types of RFC 8631: +A more complicated (and more realistic) example is when you want to indicate metainformation about the server, such as the stated policy (privacy statement and so on). We use the link types of RFC 8631:: addDOHLocal('2001:db8:1:f00::1', '/etc/ssl/certs/example.com.pem', '/etc/ssl/private/example.com.key', "/", {customResponseHeaders={["link"]=" rel=\\"service-meta\\"; type=\\"text/html\\""}})