Repository navigation
Conversation
…licy Replace referrer_concurrent_override (param referrer) with concurrent_limit, the same name ConcurrentRateLimitAllocationPolicy uses. Per-referrer values go in match blocks. default_concurrent_request_per_referrer still applies when concurrent_limit is unset. The throttle threshold now follows the effective limit.
This was referenced Oct 29, 2026
Member
Author
|
Combined into #8643. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ReferrerGuardRailPolicy's per-referrer limit is
referrer_concurrent_override(paramreferrer). This replaces it withconcurrent_limit, the same name ConcurrentRateLimitAllocationPolicy uses. Per-referrer values go in match blocks.default_concurrent_request_per_referrer, so config can move in either order.referrer_concurrent_override. No config sets it today.limit // requests_throttle_dividerof the effective limit. Before, it always useddefault_concurrent_request_per_referrer, even under an override. Same result for current config, which sets no override.No behaviour change with current config. XO's copy of the override is removed with XO in #8626.