-
Notifications
You must be signed in to change notification settings - Fork 8.4k
Improve UTF8 Tests for Invoke-WebRequest and Invoke-RestMethod #4890
Copy link
Copy link
Closed
Labels
Issue-Discussionthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifResolution-No ActivityIssue has had no activity for 6 months or moreIssue has had no activity for 6 months or moreWG-Quality-Testissues in a test or in test infrastructureissues in a test or in test infrastructure
Metadata
Metadata
Assignees
Labels
Issue-Discussionthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifResolution-No ActivityIssue has had no activity for 6 months or moreIssue has had no activity for 6 months or moreWG-Quality-Testissues in a test or in test infrastructureissues in a test or in test infrastructure
Type
Fields
Give feedbackNo fields configured for issues without a type.
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.