-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Fix Hang on when GetRequestStreamAsync #113409
Draft
liveans
wants to merge
5
commits into
dotnet:main
Choose a base branch
from
liveans:fix_httpwebrequest_nonbufferingonwrite_hang
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from 4 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
2607a60
Fix Hang on GetRequestStreamAsync in case underlying HttpClient.SendA…
liveans 169cc5b
Update src/libraries/System.Net.Requests/src/System/Net/HttpWebReques…
liveans 63b5bcb
Linux returns UnknownError for exception
liveans 8612b61
Merge branch 'fix_httpwebrequest_nonbufferingonwrite_hang' of github.…
liveans f38057a
Merge branch 'main' into fix_httpwebrequest_nonbufferingonwrite_hang
liveans File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The one thing that I've noticed is that, when user is using async path already they should implement their own timeout mechanism according to the doc: HttpWebRequest.Timeout - Remarks
Not sure, if we should stick to that behavior and limit propagating of Timeout here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
WaitAsync
will not cancel / stop the underlying tasks. What happens with them? I think this will at minimum generate unobserved exceptions.It would be better to pass the timeout to the tasks themselves via cancellation token and them catch the exception and remap to
TimeoutException
if necessary. (we do this a lot aroundHttpClient
).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like the only thing what needed in here is: removing WaitAsync because handling of Timeout will be covered by underlying HttpClient timeout anyway.
There are few cases where
getStreamTask
can never be completed.One of them is
sendRequest
is completed with cancellation or faulted, and it's already covered in this code and exception will be thrown.Second thing is that: When we set
Expect100Continue
to true, sendRequestTask will return successfully beforegetStreamTask
and if server says go away, we're going to end up waiting on getStreamTask forever, that's the case I need to figure out what framework does in that particular case.