Skip to content
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

Fixed problem with HTTP streamed mode timeout #3709

Merged
merged 1 commit into from
Jun 27, 2019

Conversation

mconnew
Copy link
Member

@mconnew mconnew commented Jun 26, 2019

We weren't passing an appropriate CancellationToken when reading from the stream.
Fixes #3590

…ropriate CancellationToken when reading from the stream
@StephenBonikowsky
Copy link
Member

@mconnew Should we add a scenario test for this?

@mconnew mconnew added the PR DO NOT MERGE If for whatever reason you do not want a PR merged. label Jun 26, 2019
@mconnew
Copy link
Member Author

mconnew commented Jun 26, 2019

Normally I'd say yes, but writing a scenario test to try and hit this would require not using WCF on the server side and taken more direct control of sending the response. As there's no logic flow change, simply propagating a timeout to calls which should have been using it, I think we can make do without scenario tests for this one.

@mconnew mconnew removed the PR DO NOT MERGE If for whatever reason you do not want a PR merged. label Jun 27, 2019
@mconnew mconnew merged commit 2ec1632 into dotnet:master Jun 27, 2019
@mconnew mconnew deleted the Issue3590 branch September 27, 2019 17:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Why timeout helper not passed to GetStreamAsync()
2 participants