BIND 10 #1626: Error: Unable to parse response from Auth: Expecting , delimiter: line 1 column 87 (char 87)

[BIND 10 Development]

#1626: Error: Unable to parse response from Auth: Expecting , delimiter: line 1
column 87 (char 87)
-------------------------------------+-------------------------------------
                   Reporter:  jreed  |                 Owner:  UnAssigned
                       Type:         |                Status:  reviewing
  defect                             |             Milestone:
                   Priority:         |  Sprint-20120403
  medium                             |            Resolution:
                  Component:         |             Sensitive:  0
  b10-auth                           |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  2
            Defect Severity:         |           Total Hours:  0
  Medium                             |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by jelte):

 * owner:  jelte => UnAssigned
 * status:  assigned => reviewing


Comment:

 So it was a missed part of the JSON conversion, really, '"' must be
 escaped, as does a number of other chars (\, \n, \t etc). AFAICT some
 implementations also escape the forward slash, so the parser code allows
 it, but we don't do so ourselves (I have tried out the python
 implementation, it accepts both too)

 With proper escaping of strings in JSON output, the quoted error message
 comes across correctly.

-- 
Ticket URL: <http://bind10.isc.org/ticket/1626#comment:13>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development