View Issue Details

IDProjectCategoryView StatusLast Update
0018268FPCPackagespublic2010-12-20 09:45
ReporterIdo Kanner Assigned ToMichael Van Canneyt  
PrioritynormalSeveritytrivialReproducibilityalways
Status closedResolutionno change required 
Product Version2.5.1 
Summary0018268: JSON parser parse string that wrapped by #32 instead of report an error
DescriptionThe JSON parser that arrives with FP, accept JSON block with 0000032 char, while according to the standard a string must be surrounded by the " char only.
Steps To Reproduce!. use the following JSON structure:

{ 'key' : 'value' }

2. Parse it using the JSON parser
3. See that it finds that 'value' is a string, and 'key' is a valid key, while it should report an error in the parser.
TagsNo tags attached.
Fixed in Revision
FPCOldBugId
FPCTarget
Attached Files

Activities

Michael Van Canneyt

2010-12-19 15:30

administrator   ~0044374

Set the 'Strict' property of the parser to 'True', then only " is accepted as string delimiter.

Some JSON producers (ExtJS jumps to mind) are more sloppy in the JSON they produce.

Issue History

Date Modified Username Field Change
2010-12-19 14:27 Ido Kanner New Issue
2010-12-19 15:27 Michael Van Canneyt Status new => assigned
2010-12-19 15:27 Michael Van Canneyt Assigned To => Michael Van Canneyt
2010-12-19 15:30 Michael Van Canneyt Status assigned => resolved
2010-12-19 15:30 Michael Van Canneyt Resolution open => no change required
2010-12-19 15:30 Michael Van Canneyt Note Added: 0044374
2010-12-20 09:45 Ido Kanner Status resolved => closed