From 62679b368a718243f865048b37808e1837e5c487 Mon Sep 17 00:00:00 2001 From: axel simon Date: Tue, 1 Feb 2022 21:45:44 +0000 Subject: [PATCH] Update route.md: fix link --- src/docs/markdown/caddyfile/directives/route.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/docs/markdown/caddyfile/directives/route.md b/src/docs/markdown/caddyfile/directives/route.md index 53e04c4..79e3e52 100644 --- a/src/docs/markdown/caddyfile/directives/route.md +++ b/src/docs/markdown/caddyfile/directives/route.md @@ -67,7 +67,7 @@ And now `file_server` will be chained in before `redir` because the order is tak There are other directives that can wrap HTTP handler directives, but each has its use depending on the behavior you want to convey: -- [`handle`](handle) wraps other directives like `route` does, but with two distinctions: 1) handle blocks are mutually exclusive to each other, and 2) directives within a handle are [re-ordered](/docs/caddyfile/directives#directive-order) normally. +- [`handle`](handle) wraps other directives like `route` does, but with two distinctions: 1) handle blocks are mutually exclusive to each other, and 2) directives within a handle are [`re-ordered`](/docs/caddyfile/directives#directive-order) normally. - [`handle_path`](handle_path) does the same as `handle`, but it strips a prefix from the request before running its handlers. - [`handle_errors`](handle_errors) is like `handle`, but is only invoked when Caddy encounters an error during request handling.