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

JSON.stringify is ambiguous with respect to upper and lowercase #1033

Closed
cyberphone opened this Issue Nov 18, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@cyberphone

cyberphone commented Nov 18, 2017

It is possible that I failed interpreting the rather massive document, but AFAICT JSON.stringify may generate "\u000f" or "\u000F" for the control character 0x000F. This collides with specifications like https://cyberphone.github.io/doc/security/jcs.html which rely on a fixed notation. Implementations appear to use the lowercase notation though.

@jmdyck

This comment has been minimized.

Show comment
Hide comment
@jmdyck

jmdyck Nov 18, 2017

Collaborator

In QuoteJSONString, step 2.c.iii says:

Let hex be the string result of converting the numeric value of C
   to a String of four lowercase hexadecimal digits.

So it isn't ambiguous with respect to upper/lowercase.

Collaborator

jmdyck commented Nov 18, 2017

In QuoteJSONString, step 2.c.iii says:

Let hex be the string result of converting the numeric value of C
   to a String of four lowercase hexadecimal digits.

So it isn't ambiguous with respect to upper/lowercase.

@cyberphone

This comment has been minimized.

Show comment
Hide comment
@cyberphone

cyberphone Nov 18, 2017

That's great. Thanx!

cyberphone commented Nov 18, 2017

That's great. Thanx!

@cyberphone cyberphone closed this Nov 18, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment