ewang

Share health across load-balancing selectors Add grouped selectors with asynchronous bounded rebuilds and shared active health across backend views.

Parameterize custom downstream sessions

let a reader stop waiting when the writer names its fill A reader coalescing behind a cache lock cannot act on anything the writer learns after the reader committed to waiting, so it waits out the full lock age even once the fill is known to be no use to it. A circular dependency can otherwise leave two participants each waiting on the lock held by the other. A writer now describes its fill with opaque `u64` tokens via `WritePermit::publish`, and a reader names the fills it cannot use in a `FillInterest` on its `CacheKey`. On a match the reader alone stops waiting; the lock status is untouched and other readers keep coalescing. Matching is integer comparison done by the cache, so no application code runs on the writer's task, and one mutex covers both published tokens and the waiter registry, making the check-then-register race impossible rather than merely unlikely. Only matching readers are woken. Each publish replaces the last: a writer that moved on is no longer doing what it said, and a reader giving up over an abandoned attempt would lose its caching for nothing. Replacing nothing with nothing cannot wake anyone, so it skips the lock rather than taking it on every upstream request. The reason rides on the token rather than the set, since a key carries one `FillInterest` and independent parts of an application share it. It travels as `NoCacheReason::Custom`, so no caller-specific cause enters the enum. `cache_lock_wait` now returns `LockWaitOutcome` rather than `LockStatus`. `LockStatus` is the lock's *shared* state, stored in an atomic and observed by every coalescing reader, so it cannot carry a payload; what happened to one reader's wait is per-reader and never stored. Separating them lets `Abandoned { reason, token }` carry its cause in the value, so there is no separate question of whether the cause was recorded, and it makes `LockStatus::Waiting` unrepresentable as a wait result -- retiring the `panic!("impossible LockStatus::Waiting")` in `handle_lock_status`. This also addresses the TODO in `handle_lock_status`, which attributed every `GiveUp` to `CacheLockGiveUp` ("the writer found the asset uncacheable") regardless of cause.

Share backends across load-balancing selectors

add owned HTTP test origin

Avoid cloning cache keys during purge

Add deferred cache admission policy hook

Close unclaimed inherited listening sockets on graceful upgrade During a zero downtime upgrade, unclaimed inherited fds were left open and transferred to later generations. With SO_REUSEPORT these sockets can black-hole connections because they remain active without an acceptor. Track complete service listen-address sets and close inherited fds not claimed after services are registered. If any service cannot report a complete set, skip cleanup. Adds coverage for both bootstrap paths and custom services.

Prevent reuse after incomplete H1 responses

pingora-proxy: reject malformed Connection nominations of protected headers Validate each Connection nomination against the HTTP `token` grammar (RFC 9110 §5.6.2) before checking it against the protected set (Host, X-Forwarded-For, X-Forwarded-Host, X-Forwarded-Proto), instead of comparing raw bytes and silently dropping tokens that fail to parse as a header name. Those two paths were mutually exclusive, so a decorated nomination like `Connection: "X-Forwarded-For"` matched no protected literal, was dropped, and the request proceeded instead of being rejected. Validating the grammar directly makes the reject independent of how permissive the header-name parser is. A protected header can never actually be stripped via nomination either way (a decorated token names a distinct header), so this hardens the fail-closed reject rather than fixing a header-stripping vulnerability. Add `HttpUpstreamRequestPolicy::reject_malformed_connection_nominations` (default true) to opt into tolerating malformed nominations as distinct literal fields, matching nginx/Envoy/Caddy. Exact protected and pseudo-header nominations are rejected either way.