Update HttpRequestMessageFactory to correctly set the Content-Length header #3631
+59
−10
Conversation
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
normj
approved these changes
Feb 1, 2025
afroz429
approved these changes
Feb 1, 2025
1 task
ashishdhingra
approved these changes
Feb 1, 2025
niemyjski
approved these changes
Feb 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Fixes #3629
Updates the .NET Standard implementation of the
HttpRequestMessageFactoryclass to consider the current stream position when setting theContent-Lengthheader (note: we have an existing test for a similar scenario but it only runs for the .NET Framework - another data point for #1181).Testing
DRY_RUN-fd5ab0eb-2c23-4fe3-9280-70cf24752fa6Types of changes
Checklist
License