[COUCHDB-333] Json handling of UTF8 strings not in accordance with rfc4627

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.9
• Component/s: Database Core

Environment

couchdb 0.9.0 spidermonkey 0.7.0 erlang R12B3

• Assignee: Unassigned
• Reporter: mark
• Created: 25/Apr/09 17:00
• Updated: 22/Feb/12 05:16
• Resolved: 08/Jun/09 14:33

Description

Handling of some unicode values escaped in json format \uXXXX fails with "invalid_json" error.

curl -X PUT -d '

{"revisions":[],"_id":"U_1d11e","codepoint":"3441","definition":"\uD834\uDD1E G clef character"}

' http://localhost:5984/mydb/U_1d11e

yields

{"error":"invalid_json","reason":"

{\"revisions\":[],\"_id\":\"U_1d11e\",\"codepoint\":\"3441\",\"definition\":\"\\uD834\\uDD1E G clef character\"}

"}

When the RFC states:
To escape an extended character that is not in the Basic Multilingual
Plane, the character is represented as a twelve-character sequence,
encoding the UTF-16 surrogate pair. So, for example, a string
containing only the G clef character (U+1D11E) may be represented as
"\uD834\uDD1E".

Furthermore, couchdb accepts encoded strings of the format \uXXXXXXXX which is not mentioned as acceptable in the json rfc

curl -X PUT -d '

{"revisions":[],"_id":"U_1d11e","codepoint":"3441","definition":"\u0001D11E G clef character"}

' http://localhost:5984/mydb/U_1d11e
Yields:

{"ok":true,"id":"U_1d11e","rev":"1-1270273433"}

Issue Links

• is related to: COUCHDB-327 Replication of document results in invalid_json error