You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 9, 2024. It is now read-only.
Streams returned from HttpClientRequestAdapter methods like SendPrimitiveAsync<Stream> cannot be used. The methods return disposed streams. I believe the culprit is the new DrainAsync method.
The text was updated successfully, but these errors were encountered:
I believe there are scenarios where the response content may be large and consumers would not want/accept to load the entire stream into memory in some scenarios. On a side note, we should also probably add support for passing the HttpCompletionOption to the httpClient as well.
I think adding a condition for streams should be okay as we already call ReadAsStreamAsync() here for streams so the connection should be released as we have read the response body.
Makes sense, thanks for the input. I'm not sure what would be the impact for the completion options (worried about side effects on the service side). Would one of you be so kind to submit a PR to add the condition to the finally please?
Streams returned from
HttpClientRequestAdapter
methods likeSendPrimitiveAsync<Stream>
cannot be used. The methods return disposed streams. I believe the culprit is the newDrainAsync
method.The text was updated successfully, but these errors were encountered: