proxy: return after writing max-retry-exhausted error - #454
Open
ZayanKhan-12 wants to merge 1 commit into
Open
Conversation
forwardRequest wrote the 502 "max retry exhausted" response when attempts reached MaxAttempts, but did not return. The loop then slept and retried anyway, and because the guard checks attempts == MaxAttempts rather than >=, it could never fire again: the loop kept retrying until the request context expired, at which point it wrote a second error response (504) on top of the 502 already sent, triggering a superfluous WriteHeader call. Every other error path in the loop returns after writeJSONError; this one now does too. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Problem
In
forwardRequest's retry loop (pkg/proxy/proxy.go), whenattemptsreachesMaxAttemptsthe proxy writes a 502max retry exhaustedresponse — but does notreturn:Two consequences:
==rather than>=, onceattemptspassesMaxAttemptsit can never fire again — so the loop keeps retrying until the request context expires, at which pointwriteJSONError(w, http.StatusGatewayTimeout, ...)writes a second response on top of the 502 already sent (http: superfluous response.WriteHeader call).Fix
Add
returnafter the error is written, matching every other error path in the loop.go build ./...,go vet ./pkg/proxy/, andgo test ./pkg/proxy/pass.🤖 Generated with Claude Code