From fb4652dc12b33ce8192428304b177e16a64017b7 Mon Sep 17 00:00:00 2001 From: DoTheEvo Date: Mon, 27 Feb 2023 17:58:03 +0100 Subject: [PATCH] update --- caddy_v2/readme.md | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/caddy_v2/readme.md b/caddy_v2/readme.md index 6f950fb..802932f 100644 --- a/caddy_v2/readme.md +++ b/caddy_v2/readme.md @@ -352,14 +352,18 @@ nextcloud.{$MY_DOMAIN} { ### Named matchers and IP filtering -Caddy has [matchers](https://caddyserver.com/docs/caddyfile/matchers) -which allow you to define how to deal with incoming requests.
-`reverse_proxy server-blue:80` is a matcher that matches all requests -and sends them somewhere.
+Caddy has [matchers](https://caddyserver.com/docs/caddyfile/matchers)
+ +* `*` to match all requests (wildcard; default). +* `/path` start with a forward slash to match a request path. +* `@name` to specify a named matcher. + +In `reverse_proxy server-blue:80` matcher is ommited and in that case +the default - `*` applies meaning all traffic. But if more control is desired, path matchers and named matchers come to play. -What if you want to block all traffic coming from the outside world, -but local network be allowed through?
+What if all traffic coming from the outside world should be blocked, but local +network be allowed through?
Well, the [remote_ip](https://caddyserver.com/docs/caddyfile/matchers#remote-ip) matcher comes to play, which enables you to filter requests by their IP.