[SERVER-11868] Strict JSON escaping Created: 26/Nov/13 Updated: 10/Dec/14 Resolved: 30/Dec/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Shaun Verch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
We should confirm that strings are escaped properly in strict-json mode, including conversion of control characters according to the rules at http://json.org/. The control characters are U+0000–U+001F, U+007F and U+0080–U+009F. Note that the last block all have multi-byte representations in UTF-8. |
| Comments |
| Comment by Githook User [ 30/Dec/13 ] |
|
Author: {u'username': u'Zarkantho', u'name': u'Shaun Verch', u'email': u'shaun.verch@10gen.com'}Message: |
| Comment by Eric Milkie [ 29/Dec/13 ] |
|
I researched a bit more and I believe you are correct. Let's stick with option 1 above. |