From daafd77ef1ebc7caa6b8c4b12f5030587ad51ad1 Mon Sep 17 00:00:00 2001 From: Francis Lavoie Date: Mon, 7 Mar 2022 12:39:19 -0500 Subject: [PATCH] Fix incorrect option name in load balancing --- 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 ea22e41..371d89e 100644 --- a/src/docs/markdown/caddyfile/directives/reverse_proxy.md +++ b/src/docs/markdown/caddyfile/directives/reverse_proxy.md @@ -168,7 +168,7 @@ Active health checks perform health checking in the background on a timer: Passive health checks happen inline with actual proxied requests: - **fail_duration** is a [duration value](/docs/conventions#durations) that defines how long to remember a failed request. A duration > 0 enables passive health checking. -- **max_fails** is the maximum number of failed requests within fail_timeout that are needed before considering a backend to be down; must be >= 1; default is 1. +- **max_fails** is the maximum number of failed requests within `fail_duration` that are needed before considering a backend to be down; must be >= 1; default is 1. - **unhealthy_status** counts a request as failed if the response comes back with one of these status codes. Can be a 3-digit status code or a status code class ending in `xx`, for example: `404` or `5xx`. - **unhealthy_latency** is a [duration value](/docs/conventions#durations) that counts a request as failed if it takes this long to get a response. - **unhealthy_request_count** is the permissible number of simultaneous requests to a backend before marking it as down.