mirror of
https://github.com/nlohmann/json.git
synced 2026-11-14 03:18:20 +00:00
Niels Lohmann
c9d30bf924
untrusted_input.md said that a string that is not valid UTF-8 in a binary format is a parse_error.113. By default the readers keep the bytes unchanged (error_handler_t::keep); only error_handler_t::strict gives parse_error.113, and BON8 always validates and reports parse_error.112. Checked with from_cbor, from_msgpack, from_ubjson, from_bjdata and from_bson (strings and keys), default and strict, and with from_bon8: default accepts the bytes, strict gives 113, BON8 gives 112 (as in tests/src/unit-bon8.cpp). Changes: - the Strings section says so, and its lead-in is limited to JSON text; - the sentence that named JSON_STRICT_NUL_HANDLING as a source of unvalidated strings (unrelated to the binary readers) now names the default error_handler_t::keep; - the checklist tells the reader to pass error_handler_t::strict to the from_* function for untrusted binary input; - json_strict_binary_utf8.md listed from_cbor as "also affected" although the same page says the binary readers behave independent of the macro, which is what the code does (verified with the macro defined to 1: from_cbor, from_msgpack and from_ubjson still accept 0xFF). Documentation only. Signed-off-by: Niels Lohmann <mail@nlohmann.me>