From: Lukáš Ježek Date: Wed, 6 May 2020 06:55:49 +0000 (+0200) Subject: doc: fix broken links X-Git-Tag: v5.1.1~2^2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=refs%2Fpipelines%2F63592;p=thirdparty%2Fknot-resolver.git doc: fix broken links --- diff --git a/doc/build.rst b/doc/build.rst index 3537eed75..8a45eaed7 100644 --- a/doc/build.rst +++ b/doc/build.rst @@ -284,7 +284,7 @@ For development, it's possible to build the container directly from your git tre .. _Docker images: https://hub.docker.com/r/cznic/knot-resolver .. _libuv: https://github.com/libuv/libuv .. _LuaJIT: http://luajit.org/luajit.html -.. _Doxygen: https://www.stack.nl/~dimitri/doxygen/manual/index.html +.. _Doxygen: https://www.doxygen.nl/manual/index.html .. _breathe: https://github.com/michaeljones/breathe .. _Sphinx: http://sphinx-doc.org/ .. _sphinx_rtd_theme: https://pypi.python.org/pypi/sphinx_rtd_theme diff --git a/modules/http/prometheus.rst b/modules/http/prometheus.rst index 233f0a6dc..acd8a8213 100644 --- a/modules/http/prometheus.rst +++ b/modules/http/prometheus.rst @@ -5,7 +5,7 @@ Prometheus metrics endpoint --------------------------- -The `HTTP module `_ exposes ``/metrics`` endpoint that serves metrics +The :ref:`HTTP module ` exposes ``/metrics`` endpoint that serves metrics from :ref:`mod-stats` in Prometheus_ text format. You can use it as soon as HTTP module is configured: diff --git a/modules/policy/README.rst b/modules/policy/README.rst index 43fa4b465..f0ff35407 100644 --- a/modules/policy/README.rst +++ b/modules/policy/README.rst @@ -61,7 +61,7 @@ It is also possible to define custom filter function with any name. :param state: Request processing state :c:type:`kr_layer_state`, typically not used by filter function. :param query: Incoming DNS query as :c:type:`kr_query` structure. - :return: An `action `_ function or ``nil`` if filter did not match. + :return: An `action <#actions>`_ function or ``nil`` if filter did not match. Typically filter function is generated by another function, which allows easy parametrization - this technique is called `closure `_. An practical example of such filter generator is: @@ -233,7 +233,7 @@ Custom actions :param state: Request processing state :c:type:`kr_layer_state`. :param request: Current DNS request as :c:type:`kr_request` structure. - :return: Returning a new :c:type:`kr_layer_state` prevents evaluating other policy rules. Returning ``nil`` creates a `chain action `_ and allows to continue evaluating other rules. + :return: Returning a new :c:type:`kr_layer_state` prevents evaluating other policy rules. Returning ``nil`` creates a `chain action <#actions>`_ and allows to continue evaluating other rules. This is real example of an action function: