- now, if client sends e.g. `Content-type: text/json;charset=[invalid]`, service will respond with HTTP/415
- if client sends `Content-type: text/json`, service will still try UTF-8 (or updated default encoding)
- intentional (and slight) behaviour change from
|
||
|---|---|---|
| .. | ||
| FormatFilterTest.cs | ||
| FormatterCollectionTest.cs | ||
| FormatterMappingsTest.cs | ||
| InputFormatterTest.cs | ||
| MediaTypeTest.cs | ||
| NoContentFormatterTests.cs | ||
| OutputFormatterTests.cs | ||
| StreamOutputFormatterTest.cs | ||
| StringOutputFormatterTests.cs | ||
| TextInputFormatterTest.cs | ||
| TextOutputFormatterTests.cs | ||