Can't handle charset Windows-1252 in responses

[djmitchella]

If the API I'm talking to has code like

Content = new StringContent(JsonConvert.SerializeObject(response), Encoding.Default, "application/json")

then the charset ends up as Windows-1252, not UTF-8, because Encoding.Default turns out to be Windows-1252 in this situation.

httprepl can't handle this charset, so instead of the body from the server, I get an error from httprepl itself -- in this case I'm getting an error back from the server, and the body is encoded this way:

The headers returned are:

HTTP/1.1 401 Unauthorized
Access-Control-Allow-Origin: *
Cache-Control: private
Content-Length: 41
Content-Type: application/json; charset=Windows-1252
Date: Fri, 20 Sep 2019 19:34:56 GMT

and then the error from httprepl itself is:

System.InvalidOperationException: The character set provided in ContentType is invalid. Cannot read content as string using an invalid character set. ---> System.ArgumentException: 'Windows-1252' is not a supported encoding name. For information on defining a custom encoding, see the documentation for the Encoding.RegisterProvider method.

In this case, I control the API as well so I can change the encoding there, but it would be nice if httprepl could manage this charset itself.