v0.25.6

docs/VHOSTS.md

@@ -194,13 +194,21 @@ origin do not expose a selected backend or stale origin timing.
 | `idle_timeout_seconds` | 30 | 1..3600 |
 | `max_idle_per_host` | 4 | 1..64 |
 | `tcp_keepalive_seconds` | 30 | 1..3600 |
+| `pool_recycle_requests` | 25000 | 0 (off) or 1000..10000000 |
+| `pool_recycle_seconds` | 3600 | 0 (off) or 60..604800 |
+| `http1_max_buffer_bytes` | 131072 | 8192..1048576 |
 
 These configure HTTP idle reuse and TCP keepalive; HTTP/2 also uses pings for active
 connections, with a 10-second ping timeout and no pinging solely to keep idle
-connections alive. Disabling reuse sets the idle pool limit to zero and disables
-those keepalive probes. It does not abort already active requests/tunnels. The idle
-limit is not a separate per-backend active-request cap; global connection/exchange
-bounds still apply. HTTP health probes use separate no-reuse HTTP/1.1 connections.
+connections alive. `pool_recycle_requests` and `pool_recycle_seconds` bound the lifetime
+of each backend Hyper client generation. Recycling swaps only that backend client/pool;
+it does not reload the vhost, purge cache or intentionally abort active exchanges. The
+request counter is per backend client generation, not per TCP connection. Setting either
+recycle value to `0` disables that trigger independently. `http1_max_buffer_bytes` bounds
+Hyper's adaptive upstream HTTP/1 read buffer per connection; it does not apply to HTTP/2.
+Disabling reuse sets the idle pool limit to zero and disables keepalive probes. The idle
+limit is not a separate per-backend active-request cap; global connection/exchange bounds
+still apply. HTTP health probes use separate no-reuse HTTP/1.1 connections.
 
 `http2` over HTTPS prefers h2 but keeps HTTP/1.1 ALPN compatibility. Over plaintext,
 `http2` remains explicit prior-knowledge h2c with no retry-based downgrade. `auto`