CODEWITHSUNDEEP
jsonyajl
SecResearcher
SecResearcher

Reputation: 11

Is representing {"some":"thing\n"} - json object into a unicode considered valid json?

According to JSON RFC: A JSON text is a sequence of tokens. The set of tokens includes six structural characters, strings, numbers, and three literal names.

A JSON text is a serialized object or array.

  JSON-text = object / array

These are the six structural characters:

  begin-array     = ws %x5B ws  ; [ left square bracket

  begin-object    = ws %x7B ws  ; { left curly bracket

  end-array       = ws %x5D ws  ; ] right square bracket

  end-object      = ws %x7D ws  ; } right curly bracket

  name-separator  = ws %x3A ws  ; : colon

  value-separator = ws %x2C ws  ; , comma

Insignificant whitespace is allowed before or after any of the six structural characters.

  ws = *(
            %x20 /              ; Space
            %x09 /              ; Horizontal tab
            %x0A /              ; Line feed or New line
            %x0D                ; Carriage return
        )

So I can represent '{' and '}' as unicode characters? If I convert the JSON object - {"some":"thing\n"} to unicode, it is represented as: \u007B\u0022\u0073\u006F\u006D\u0065\u0022\u003A\u0022\u0074\u0068\u0069\u006E\u0067\u006E\u0022\u007D Why does the YAJL parser gives error to this then? If I modify the input as "\u0022\u0073\u006F\u006D\u0065\u0022\u003A\u0022\u0074\u0068\u0069\u006E\u0067\u006E\u0022" - It can parse it without any error. Does anyone know the reason behind this?

Upvotes: 1

Views: 194

Answers (0)

Related Questions