-
Notifications
You must be signed in to change notification settings - Fork 10.4k
HTTP/3: Raise RequestAbort on client cancellation #34675
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
Conversation
|
||
var serverWriteTask = await readAsyncTask.Task.DefaultTimeout(); | ||
|
||
var ex = await Assert.ThrowsAnyAsync<OperationCanceledException>(() => serverWriteTask).DefaultTimeout(); |
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.
If the request is aborted and ReadAsync or WriteAsync are called on the server, what should the exception type be? I think HTTP/2 throws IOException...
3482a8e
to
4f6b17e
Compare
{ | ||
// TODO: This is temporary. Don't want to tie HTTP/3 layer to one transport. | ||
// This is here to check what other exceptions can cause ConnectionResetException. | ||
Debug.Assert(ex.InnerException is QuicStreamAbortedException); |
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.
This really only affects local development, right? I'm not sure this is worth checking in especially if we're not confident in it. Maybe just keep it as a stash you reapply locally? I guess it's not a big deal either way.
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.
Yes.
I want to check because I'm not confident and I want it to break locally
Fixes #34674