[dotnet] Fix network response data encoding #13576
Merged
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
NetworkManager exposes HTTP response body data as
string
type. Not all responses have strings. In case if the response is bytes, selenium is doing extra convertion frombytes
toutf8 string
. It leads to data loosing, we cannot convert string back to bytes.Motivation and Context
Fix #11726
New approach to get data
And its output is:
where
6255
is correct bytes of the image.Types of changes
Checklist