From cd192a65c4cb391e3e2678221b0158f7c9882d54 Mon Sep 17 00:00:00 2001 From: Marco Bernasocchi Date: Thu, 13 Feb 2020 21:21:26 +0100 Subject: [PATCH] Clarify that the JSON doc is the doc for matchers --- src/docs/markdown/caddyfile/concepts.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/docs/markdown/caddyfile/concepts.md b/src/docs/markdown/caddyfile/concepts.md index 767d489..6a65e21 100644 --- a/src/docs/markdown/caddyfile/concepts.md +++ b/src/docs/markdown/caddyfile/concepts.md @@ -160,7 +160,7 @@ An address must be unique; you cannot specify the same address more than once. By default, a directive that injects an HTTP handler applies to all requests (unless otherwise documented). -**Request matchers** can be used to classify requests by a given criteria. This concept originates in the [underlying JSON](/docs/json/apps/http/servers/routes/match/) structure, and it's important to know how to use them in the Caddyfile. With matchers, you can specify exactly which requests a directive applies to. +**Request matchers** can be used to classify requests by a given criteria. This concept originates in the underlying JSON structure which also serves as [matcher documentation](/docs/json/apps/http/servers/routes/match/), and it's important to know how to use them in the Caddyfile. With matchers, you can specify exactly which requests a directive applies to. To limit a directive's scope, use a **matcher token** immediately after the directive. It can be one of these forms: @@ -356,4 +356,4 @@ If present, it must be the very first block in the config. It is used to set options that apply globally, or not to any one site in particular. Inside, only global options can be set; you cannot use regular site directives in them. -[Learn more](/docs/caddyfile/options) about the global options block. \ No newline at end of file +[Learn more](/docs/caddyfile/options) about the global options block.