We should add the standard disclaimer “(with line breaks within values for
display purposes only)” to the description of the example.
-- Mike
From: jose [mailto:[email protected]] On Behalf Of Mark Watson
Sent: Tuesday, January 13, 2015 8:53 AM
To: Anders Rundgren
Cc: Richard Barnes; [email protected]
Subject: Re: [jose] "x5c" - JSON Compatible?
On Tue, Jan 13, 2015 at 4:13 AM, Anders Rundgren
<[email protected]<mailto:[email protected]>> wrote:
On 2015-01-13 12:35, Richard Barnes wrote:
On Tuesday, January 13, 2015, Anders Rundgren
<[email protected]<mailto:[email protected]>
<mailto:[email protected]<mailto:[email protected]>>>
wrote:
The spec claims the following:
"Note that since these strings contain base64 encoded
(not base64url encoded) values, they are allowed to contain
white space and line breaks."
Is this really JSON compliant?
I didn't interpret the JSON spec in that way and Python and Chrome seems to
agree with me.
What's I'm missing here?
Are you seriously suggesting that JSON strings can't contain white space?
Control characters have to be escaped, but they can definitely be there.
JSON.parse('["this is...\\u000A...a string"]')
Sure, but the example in appendix B wouldn't parse.
Shouldn't a proper text say that possible line-breaks MUST be properly escaped.
Line breaks in JSON do have to be escaped, either as above or with \r \n. This
is clear at www.json.org<http://www.json.org>.
…Mark
Anders
--Richard
Cheers
Anders
_________________________________________________
jose mailing list
[email protected]<mailto:[email protected]>
https://www.ietf.org/mailman/__listinfo/jose
<https://www.ietf.org/mailman/listinfo/jose>
_______________________________________________
jose mailing list
[email protected]<mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/jose
_______________________________________________
jose mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/jose
