Repository navigation
Improve UTF8 Tests for Invoke-WebRequest and Invoke-RestMethod #4890
Description
The current tests (soon to be) added in #4869 are an improvement from before but, perhaps, some better tests could be added.
Possibilities include ensuring there are no UTF16 or UTF32 chars, generating UTF8 from the WebListener controller instead of using a view, etc.
Also after #4888, a check can be made on the response headers from Invoke-RestMethod.
Activity
[-]Improve UTF8 Tests for Invoke-WebRequest and Invoke-Restmethod[/-][+]Improve UTF8 Tests for Invoke-WebRequest and Invoke-RestMethod[/+]iSazonov commentedon Sep 22, 2017
We could look how our file encoding tests works.
Also I believe it make sense to use `u{...} in test file if we need a constant test string - it protect our tests if we change the file encoding.
microsoft-github-policy-service commentedon Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commentedon Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commentedon Nov 16, 2023
This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commentedon Nov 23, 2023
This issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes.