Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Why aren't double quotes and backslashes allowed in strings in the JSON standard?

If I run this in a JavaScript console in Chrome or Firebug, it works fine.

JSON.parse('"\u0027"') // Escaped single-quote

But if I run either of these 2 lines in a Javascript console, it throws an error.

JSON.parse('"\u0022"') // Escaped double-quote
JSON.parse('"\u005C"') // Escaped backslash

RFC 4627 section 2.5 seems to imply that \ and " are allowed characters as long as they're properly escaped. The 2 browsers I've tried this in don't seem to allow it, however. Is there something I'm doing wrong here or are they really not allowed in strings? I've also tried using \" and \\ in place of \u0022 and \u005C respectively.

I feel like I'm just doing something very wrong, because I find it hard to believe that JSON would not allow these characters in strings, especially since the specification doesn't seem to mention anything that I could find saying they're not allowed.

like image 794
Dan Herbert Avatar asked Jan 02 '11 02:01

Dan Herbert


People also ask

Can you use double quotes inside a JSON string?

Strings in JSON are specified using double quotes, i.e., " . If the strings are enclosed using single quotes, then the JSON is an invalid JSON .

Why does JSON require double quotes?

Yes. Properties in JSON have to be strings, and in JSON as string is defined as "a sequence of zero or more Unicode characters, wrapped in double quotes, using backslash escapes". In other words using single quotes, or no quotes at all is not allowed.

Should I use single or double quotes in JSON?

As said, JSON is not Python syntax. You need to use double quotes in JSON. Its creator is (in-)famous for using strict subsets of allowable syntax to ease programmer cognitive overload.

Are single and double quotes the same JSON?

As you can see from the code snippet, single quotes break JSON parsing. The technical reason has to do with the JSON specification (RFC 7159), which requires double quotes as the JSON string character.


2 Answers

You need to quote the backslash!

that which we call a rose

By any other name would smell as sweet

A double quote is a double quote, no matter how you express it in the string constant. If you put a backslash before your \u expression within the constant, then the effect is that of a backslash-quoted double-quote, which is in fact what you've got.

The most interesting thing about your question is that it helps me realize that every JavaScript string parser I've ever written is wrong.

like image 59
Pointy Avatar answered Sep 21 '22 10:09

Pointy


JavaScript is interpreting the Unicode escape sequences before they get to the JSON parser. This poses a problem:

  • '"\u0027"' unquoted the first time (by JavaScript): "'"
    The second time (by the JSON parser) as valid JSON representing the string: '

  • '"\u0022"' unquoted the first time (by JavaScript): """
    The JSON parser sees this unquoted version """ as invalid JSON (does not expect the last quotation mark).

  • '"\u005C"' unquoted the first time (by JavaScript): "\"
    The JSON parser also sees this unquoted version "\" as invalid JSON (second quotation mark is backslash-escaped and so does not terminate the string).

The fix for this is to escape the escape sequence, as \\u.... In reality, however, you would probably just not use the JSON parser. Used in the correct context (ensured by wrapping it within parentheses, all JSON is valid JavaScript.

like image 31
PleaseStand Avatar answered Sep 18 '22 10:09

PleaseStand