|
|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
[2018-02-20 14:00 UTC] welfordmartin at gmail dot com
Description:
------------
When using json_decode to decode a string value containing "{" or "}" the validation fails and it does not produce an object this even happens when both are UTF-8 encoded with "\x7B" and "\x7D" respectfully. both cases cause a 'JSON_ERROR_SYNTAX',
While the JSON code has been manually checked against the RFC4627 and it says standard C strings well I can't believe I have to point this one out to you but using "{" and "}" are both ASCII chars so valid in a string.
The JSON also parses correctly in Web Browsers both Chrome, Edge & IE parsers.
JSON Code used:
{
"defaultModel":"Campaign",
"routes" : {
"getCampaignsForWebsite":{
"scope" : "read_campaigns",
"api":{
"method" : "GET",
"uri" : "/campaign/\x7BdisplayType\x7D/\x7Bwebsite_id:\d+\x7D"
},
"perms":{
"module" : "website",
"requirement" : "read"
}
},
"getSingleCampaign":{
"scope" : "read_campaigns",
"api":{
"method" : "GET",
"uri" : "/campaign/\x7Bcampaign_id:\d+\x7D"
},
"perms":{
"module" : "campaign",
"requirement" : "read"
}
}
}
}
Test script:
---------------
$raw = file_get_contents("test.json");
$json = json_decode($raw, true);
switch (json_last_error()) {
case JSON_ERROR_NONE:
echo ' - No errors';
break;
case JSON_ERROR_DEPTH:
echo ' - Maximum stack depth exceeded';
break;
case JSON_ERROR_STATE_MISMATCH:
echo ' - Underflow or the modes mismatch';
break;
case JSON_ERROR_CTRL_CHAR:
echo ' - Unexpected control character found';
break;
case JSON_ERROR_SYNTAX:
echo ' - Syntax error, malformed JSON';
break;
case JSON_ERROR_UTF8:
echo ' - Malformed UTF-8 characters, possibly incorrectly encoded';
break;
default:
echo ' - Unknown error';
break;
}
Expected result:
----------------
I expect an array result when using assoc or a stdClass object when not.
Actual result:
--------------
Null and json_last_error results in JSON_ERROR_SYNTAX
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
|
|||||||||||||||||||||||||||
Copyright © 2001-2024 The PHP GroupAll rights reserved. |
Last updated: Thu Apr 18 19:01:30 2024 UTC |
> Since backslash d (\d) is not one of the listed escapes allowed it should be evaluated to unescaped (literal) "\" and "d"? as that is exactly what that standard. with unescaped or escape one of this list it is explicitly a / meaning or. No, "\" may be followed **only** by the characters listed there. Note that the "unescaped" production explicitly excludes "\". > also, the UTF-8 encoded was tried after I mean to set it back to bracers before posting it in the bug. Did you use both \\d and {} or \uXXXX escape sequences? If you still had \d the JSON would still be invalid.> Please tell me where in that specification it states only it sates "unescaped / escape ( ... )" that in English means "unescaped or escape ( ... ) " and Javascript engines agree with that statement as they work in parsing that JSON. even IE. I'm sorry, I don't know how I can explain this to you. There is simply no way for this grammar to accept the sequence "\d". It does not match as "unescaped" because "\" is not allowed in unescaped. It does not match "escaped", because "\" cannot be followed by "d". >The representation of strings is similar to conventions used in the C >family of programming languages. A string begins and ends with >quotation marks. All Unicode characters may be placed within the >quotation marks except for the characters that must be escaped: >quotation mark, reverse solidus, and the control characters (U+0000 through U+001F) This quite explicitly says "[...] except for the characters that must be escaped: [...] reverse solidus [...]". "\" is a reverse solidus. "\" must be escaped. > Since \d is not a valid escape it should be literal the same as the conventions in c family langs. most if not all including PHP fall back to string escape is not valid use literal. It's nice that you think this way, but this is not what the JSON specification says and consequently not what PHP does. Also, your claim that JavaScript implementations follow the behavior you describe is incorrect. If you write JSON.parse("\"\\d\"") you will receive a syntax error. You need to use JSON.parse("\"\\\\d\"") instead. What you probably tried is to simply parse the JSON as JS, which has entirely different and much less strict rules. If you want to parse JS, please use a JS parser, not a JSON parser.