-
Notifications
You must be signed in to change notification settings - Fork 1.6k
BodyDefferingAsyncHandler should not retry #1555
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Contribution would be greatly appreciated. |
I would but I cannot push the branch it seems.
|
Of course you can't push on this repository! |
Fork a complete repo under my account and then push a PR on this fork? Then you grab the changes? Sounds quite overkill to me - here's a patch. |
Please understand that pull requests are the more convenient for people who maintain open source projects (and who are usually swamped and do OSS on their free time):
So please go with the standard process. |
Great, thanks! |
Closed by #1560 |
Hi
I found out that the BodyDefferingAsyncHandler does not play well with the default retries on GET.
If the connection is closed after the caller thread has started consuming the body, the default behavior of the client is to retry the request, pouring the new body into the same output stream as the first request.
Unless I'm mistaken BodyDefferingAsyncHandler should overwrite 'onRetry' and throw an exception there, unless there's a cleaner way to do this.
The current workaround is to configure the client with 0 retries, but as it is global, that's not a good solution.
The text was updated successfully, but these errors were encountered: