Fix to fallback to utf-8 when provided an invalid charset in web responses - #27789
Open
Ryan Yates (kilasuit) wants to merge 1 commit into
Open
Fix to fallback to utf-8 when provided an invalid charset in web responses#27789Ryan Yates (kilasuit) wants to merge 1 commit into
Ryan Yates (kilasuit) wants to merge 1 commit into
Conversation
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
This file contains hidden or 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
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.
PR Summary
This adds in the conversion when servers respond with
charset=utf8& other non recognised charsets.By doing so the Debug message that contains the WebResponse Body is returned as expected by developers or end users of the WebCmdlets
PR Context
fixes #27788
PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright header