Properly drain failed responses in http-service-composition example #3026
Conversation
This file contains 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
Motivation: Existing `ResponseCheckingClientFilter` demonstrated in `servicetalk-http-service-composition` maps the response to an exception, but does not drain the response payload body, leaking the connection. Modifications: - Replace `ResponseCheckingClientFilter` with `RetryingHttpRequesterFilter.Builder.requestMapper` feature; - Rename `BadResponseHandlingServiceFilter` to `HttpResponseExceptionHandlingServiceFilter` and update it to target `HttpResponseException` instead of `BadResponseStatusException`; Result: We don't show users how to leak a connection :)
Scottmitch
approved these changes
Jul 31, 2024
bryce-anderson
approved these changes
Jul 31, 2024
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.
Motivation:
Existing
ResponseCheckingClientFilterdemonstrated inservicetalk-http-service-compositionmaps the response to an exception, but does not drain the response payload body, leaking the connection.Modifications:
ResponseCheckingClientFilterwithRetryingHttpRequesterFilter.Builder.requestMapperfeature;BadResponseHandlingServiceFiltertoHttpResponseExceptionHandlingServiceFilterand update it to targetHttpResponseExceptioninstead ofBadResponseStatusException;Result:
We don't show users how to leak a connection :)