Fix 'no response returned' RuntimeError during cancellation in BaseHTTPMiddleware #2519
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.
Fixes: #2516
If an incoming request is disconnected before a response gets produced, don't raise a RuntimeError. This fixes a race condition that occurs when many
BaseHTTPMiddleware
instances are wrapped within each other and the client (e.g., web browser) disconnects before the start of the response has been produced by the endpoint.An alternative fix, possibly better, would be to always return a dummy
Response
and never raise theRuntimeError
, regardless of whether_is_disconnected
is set.Checklist