> (3) The default transfer encoding syntax is UTF-8. Notice that the RFC is partially irrelevant. It only applies to the application/json mime type, and JSON is used in various other protocols, using various other encodings. > I think it's a bad idea for any of the core > JSON API to accept or produce bytes in any language that provides a > Unicode string type. So how do you integrate the encoding detection that the RFC suggests to be done? Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4