feat(renderer): proxy-retry on origin rate-limit (429)#194
Merged
Conversation
An HTTP fetch the origin rate-limits with 429 is now retried ONCE through a configured proxy (`CRW_HTTP_RATELIMIT_PROXY_URL`, e.g. a residential/datacenter gateway) — a different egress IP usually clears the limit, so the engine no longer stalls behind a single shared egress IP when a large proxy pool is available. Opt-in: unset/empty = behavior identical to before. Mirrors the relaxed-TLS fallback (a per-trigger fallback client + a one-shot flag in the fetch loop, no retry-budget consumption). The cert/relaxed and transient-retry paths are untouched; SSRF protection is unaffected (it runs on the resolved target URL, not the proxy hop).
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
1 participant
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.
A 429 (origin rate-limiting our egress IP) now triggers ONE retry through a configured proxy (
CRW_HTTP_RATELIMIT_PROXY_URL) — a different egress IP clears the limit, so the engine stops stalling behind a single shared IP when a large proxy pool is available. Opt-in (unset=unchanged). Mirrors the relaxed-TLS fallback; SSRF unaffected. Fixes the real-world case where high-volume scraping (or multi-engine scale tests) hit per-IP rate-limits.