-
-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parsing and serialization of control characters #103
Comments
Cannot see the sample (it 404's for me). Can you point me at the offending JSON grammar language that the lib is violating by any chance? Happy to have this fixed, but just wanna know where it says! |
Sorry, the repository was still set to "private". It should be public now. I am referencing Section 7 "Strings" from (https://datatracker.ietf.org/doc/html/rfc8259):
If my understanding of this is correct, the control characters below U+001F must be passed as "\u0000" - "\u001f" to be valid JSON (except for U+0008, U+000C, U+000A, U+000D, U+0009 which may also be passed as "\b", "\f", "\n", "\r", "\t"). json.h behaves as follows: These are expected to return parsing errors:
These are expected to be parsed and return "\u00xx":
Note that since there is also Section 9 "Parser", json.h is technically still adhering to the specification. So feel free to decide on the correct way to handle this.
|
Nice summary thanks! I think we'll fix this - seems worthwhile to err on the side of caution here. I can take this change up if you wish, but happy to accept a PR if you'd rather do the coding! |
Hi, sorry for the late reply. Unfortunately, I am not that familiar with the code base, so I think it would be better, if you implemented the necessary changes. |
Totally fine. When I get the time I'll look into it. |
Hello,
we found json.h to parse and serialize control characters below 0x20 which technically is in violation of the JSON grammar. We collected a minimum working sample here.
The text was updated successfully, but these errors were encountered: