René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Invoke-WebRequest should support -Encoding parameter for default character set","articleBody":"### Summary of the new feature / enhancement\n\nThis is a follow up to https://github.com/PowerShell/PowerShell/issues/19156\r\n\r\nOther cmdlets use an \"-Encoding\" parameter, eg Get-Content. It would be nice if this was used for the default encoding character set when the character set is not present in the ContentType and the body is some form of string rather than binary. This would be better than treating certain MIME types as somehow special.\n\n### Proposed technical implementation details (optional)\n\nThe Invoke-WebRequest refers to a default character set but it is not clear how this is determined, and the behaviour is different between 7.3.3 and powershell-7.4.0-preview.1\r\n\r\nThe concept is to use the \"-Encoding\" parameter to specify the default character set if it is not present in the MIME type.\r\n\r\nAn example is \"application/json\" is technically a binary encoding so should not have the charset in the ContentType. \r\n\r\nIt would be better to use an explicit \"-Encoding\" parameter than maintain a list of special MIME types that need particular character set encodings.","author":{"url":"https://github.com/rhubarb-geek-nz","@type":"Person","name":"rhubarb-geek-nz"},"datePublished":"2023-02-26T10:46:35.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":18},"url":"https://github.com/19226/PowerShell/issues/19226"}