From 59dfaa199316fcc4687fdde779c2024390719fb6 Mon Sep 17 00:00:00 2001 From: Francis Lavoie Date: Mon, 23 Nov 2020 23:07:44 -0500 Subject: [PATCH] docs: Add cookie hash policy for proxy --- src/docs/markdown/caddyfile/directives/reverse_proxy.md | 1 + 1 file changed, 1 insertion(+) diff --git a/src/docs/markdown/caddyfile/directives/reverse_proxy.md b/src/docs/markdown/caddyfile/directives/reverse_proxy.md index 7286ee6..5719c8f 100644 --- a/src/docs/markdown/caddyfile/directives/reverse_proxy.md +++ b/src/docs/markdown/caddyfile/directives/reverse_proxy.md @@ -81,6 +81,7 @@ Load balancing is used whenever more than one upstream is defined. - `random_choose ` - selects two or more upstreams randomly, then chooses one with least load (`n` is usually 2) - `round_robin` - iterate each upstream in turn - `uri_hash` - map URI to sticky upstream + - `cookie [ []]` - based on the given cookie (default name is `lb` if not specified), whose 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. - **lb_try_interval** is a [duration value](/docs/conventions#durations) that defines how long to wait between selecting the next host from the pool. Default is `250ms`. Only relevant when a request to an upstream host fails. Be aware that setting this to 0 with a non-zero `lb_try_duration` can cause the CPU to spin if all backends are down and latency is very low.