From 8d5d93b37968b4a07d6f4f9fab87f98ffb19658e Mon Sep 17 00:00:00 2001 From: Dan Cecile Date: Thu, 2 Jan 2025 22:40:21 -0500 Subject: [PATCH] reverse_proxy: Describe using zero for weighted round robin (#437) The old restriction is lifted now that https://github.com/caddyserver/caddy/pull/6681 is merged and released in 2.9.0 --- 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 bb47c74..363d3d2 100644 --- a/src/docs/markdown/caddyfile/directives/reverse_proxy.md +++ b/src/docs/markdown/caddyfile/directives/reverse_proxy.md @@ -275,7 +275,7 @@ This is enabled by default, with the `random` policy. Retries are disabled by de - `round_robin` iterates each upstream in turn - - `weighted_round_robin ` iterates each upstream in turn, respecting the weights provided. The amount of weight arguments should match the amount of upstreams configured. Weights should be non-zero positive integers. For example with two upstreams and weights `5 1`, the first upstream would be selected 5 times in a row before the second upstream is selected once, then the cycle repeats. + - `weighted_round_robin ` iterates each upstream in turn, respecting the weights provided. The amount of weight arguments should match the amount of upstreams configured. Weights should be non-negative integers. For example with two upstreams and weights `5 1`, the first upstream would be selected 5 times in a row before the second upstream is selected once, then the cycle repeats. If zero is used as a weight, this will disable selecting the upstream for new requests. - `least_conn` choose upstream with fewest number of current requests; if more than one host has the least number of requests, then one of those hosts is chosen at random