From 3fa3b2ceaeb7b21acee0e0a654cc44e950599ce6 Mon Sep 17 00:00:00 2001 From: Matt Holt Date: Wed, 1 Jun 2022 16:03:57 -0600 Subject: [PATCH] Update src/docs/markdown/caddyfile/directives/reverse_proxy.md --- 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 4c20ef5..bc047b1 100644 --- a/src/docs/markdown/caddyfile/directives/reverse_proxy.md +++ b/src/docs/markdown/caddyfile/directives/reverse_proxy.md @@ -216,7 +216,7 @@ Load balancing is used whenever more than one upstream is defined. - `least_conn` - choose upstream with fewest number of current requests - `ip_hash` - map client IP to sticky upstream - `uri_hash` - map URI to sticky upstream - - `header [field]` - map request header to sticky upstream. If the specified header is not present, a random upstream is selected + - `header [field]` - map request header to sticky upstream. If the specified header is not present, a random upstream is selected. - `cookie [ []]` - based on the given cookie (default name is `lb` if not specified), which value is hashed; optionally with a secret for HMAC-SHA256 - **lb_try_duration** is a [duration value](/docs/conventions#durations) that defines how long to try selecting available backends for each request if the next available host is down. By default, this retry is disabled. Clients will wait for up to this long while the load balancer tries to find an available upstream host.