IHttpRequestBodyDetectionFeature
for HTTP/3 GET requests
#62275
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.
IHttpRequestBodyDetectionFeature
for HTTP/3 GET requestsIHttpRequestBodyDetectionFeature
returns false for HTTP/3 (bodyless) GET requestsDescription
IHttpRequestBodyDetectionFeature
to include HTTP/3 descriptions for theEND_STREAM
flag.Http3Stream
modified request body handling logic to return zero length content body instance when there endstream flag is set. It also completes the message body for empty requests, so that theRequestBodyPipe.Reader
is closed (needs to be closed, so that when the stream is reused by the pool, the Pipe is reset which requires closed reader) - not sure if this is the best place to do this.CanHaveBody_ReturnsFalseWithoutRequestBody
to validate behavior when no request body is present.Fixes #58753