From dd191b380f19fac764becc5dfd563b604e8cb8b0 Mon Sep 17 00:00:00 2001 From: Dan Farino <91212675+danfarinoeyecue@users.noreply.github.com> Date: Tue, 16 Aug 2022 18:58:40 -0700 Subject: [PATCH] remove extra word (#252) --- src/docs/markdown/caddyfile/directives/reverse_proxy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/docs/markdown/caddyfile/directives/reverse_proxy.md b/src/docs/markdown/caddyfile/directives/reverse_proxy.md index 95e8601..8777104 100644 --- a/src/docs/markdown/caddyfile/directives/reverse_proxy.md +++ b/src/docs/markdown/caddyfile/directives/reverse_proxy.md @@ -531,7 +531,7 @@ When a response handler is invoked, the response from the backend is not written - **@name** is the name of a [response matcher](#response-matcher). As long as each response matcher has a unique name, multiple matchers can be defined. A response can be matched on the status code and presence or value of a response header. - **replace_status** simply changes the status code of response when matched by the given matcher. -- **handle_response** defines the route to execute when matched by the given matcher (or, if a matcher is omitted, all responses). The first matching block will be applied. Inside a `handle_response` block, any other [directives](/docs/caddyfile/directives) can be used. During +- **handle_response** defines the route to execute when matched by the given matcher (or, if a matcher is omitted, all responses). The first matching block will be applied. Inside a `handle_response` block, any other [directives](/docs/caddyfile/directives) can be used. Additionally, inside `handle_response`, two special handler directives may be used: