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:  muks
                       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 => muks


Comment:

 hehe, we're venturing well out of scope here, but good catch :)

 The reason extra data was allowed is that all was based on streams; but of
 course checking for 'end' if the input is a string is not much of a
 problem; even found some bad input in a completely unrelated python test
 :)

 Also replaced all those direct lists of characters with one WHITESPACE
 const.

 BTW, I also moved a few of these test cases; some don't have much to do
 with escaping, but with general 'whitespace' handling in conversion, so
 i've moved those to the relevant tests.

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