json_encode

JSON

Last updated: Sun, 25 Nov 2007

json_decode

(PHP 5 >= 5.2.0, PECL json:1.2.0-1.2.1)

json_decode — Decodes a JSON string

설명

mixed json_decode ( string $json [, bool $assoc ] )

Takes a JSON encoded string and converts it into a PHP variable.

매개변수

json: The json string being decoded.
assoc: When TRUE, returned objects will be converted into associative arrays.

반환값

Returns an object or if the optional assoc parameter is TRUE, an associative array is instead returned.

예제

Example#1 json_decode() examples


<?php
$json = '{"a":1,"b":2,"c":3,"d":4,"e":5}';

var_dump(json_decode($json));
var_dump(json_decode($json, true));

?>

위 예제의 출력:

object(stdClass)#1 (5) {
    ["a"] => int(1)
    ["b"] => int(2)
    ["c"] => int(3)
    ["d"] => int(4)
    ["e"] => int(5)
}

array(5) {
    ["a"] => int(1)
    ["b"] => int(2)
    ["c"] => int(3)
    ["d"] => int(4)
    ["e"] => int(5)
}

주의

Caution

This function will return false if the JSON encoded data is deeper than 127 elements.

변경 기록

버전	설명
5.2.3	The nesting limit was increased from 20 to 128

참고

json_encode()

json_encode

JSON

Last updated: Sun, 25 Nov 2007

add a note User Contributed Notes
json_decode

coyote4til7 at gmail dot com
22-Jul-2008 08:22


FWIW, the code behind json_decode is using an overly strict interpretation of the JSON spec.  If you're feeding json encoded from the browser and the object keys (or member names in JSON terms) are not quoted, json_decode fails.  



So, if you're hoping to parse JSON that also can be properly handled by Javascript's eval, you're going to have to use another tool.  I'm usuing the json toolkit in xml-rpc for php (check sourceforge) quite successfully.



This seems like a bug to me, but when I reported it as a bug (#45563), it was marked bogus.

ganswijk at xs4all dot nl
06-Jul-2008 07:42


It was quite hard to figure out the allowed Javascript formats. Some extra remarks:



json_decode() doesn't seem to allow single quotes:

<?php

print_r(json_decode('[0,{"a":"a","b":"b"},2,3]'));  //works

print_r(json_decode("[0,{'a':'a','b':'b'},2,3]"));  //doesn't work

?>



json_decode() doesn't allow an extra comma in a list of entries:

<?php

print_r(json_decode('[0,1 ]'));  //works

print_r(json_decode('[0,1,]'));  //doesn't work

?>



(I like to write a comma behind every entry when the entries are spread over several lines.)



json_decode() does allow linefeeds in the data!

?>

xris / a t/ basilicom.de
27-Jun-2008 08:48


Please note: in javascript, the following is a valid object:

<?php

   { bar: "baz" }

?>



While PHP needs double quotes:



<?php

  { "bar": "baz" }

?>

phpben
16-Apr-2008 12:18


Re requiring to escape the forward slash:



I think PHP 5.2.1 had that problem, as I remember it occurring here when I posted that comment; but now I'm on 5.2.5 it doesn't, so it has obviously been fixed. The JSON one gets from all the browsers escape the forward slashes anyway.

Hayley Watson
08-Apr-2008 02:40


@AMA3:

"It's strange that forward-slash is permitted to be escaped but not required to be, and that it has the same meaning either way, but that's how it's written, and so shall it be."



JavaScript ignores '\' characters that don't start any sort of escape sequence, so as far as it is concerned, "\/" is equivalent to "/" (ECMA-262, §7.8.4). So in that sense it's permitted but not required to be: so why do it?



json_encode("</script>") will produce "<\/script>" so that HTML parsers don't see a </script> end tag and choke on it (to play it safe and simplify the implementation, it escapes all '/'s); json_decode() therefore has to cope with that.



As for it being necessary, I agree: it isn't on MY machine :)



json_decode('{"a":"<p>test<\/p>"}'); ==> (object)array('a' => '<p>test</p>');



json_decode('{"a":"<p>test</p>"}'); ==> (object)array('a' => '<p>test</p>');

Hayley Watson
08-Apr-2008 02:04


In relation to yasarbayar's comment:



Remember that JSON strings are JavaScript code and have JavaScript syntax. In PHP, arrays and associative arrays are the same thing but that's not true in JavaScript, where "associative arrays" are really objects. [] is an array initializer, {} creates objects:



{30:'13',31:'14',32:'15'}

Bad: JavaScript object initialiser, but object property names can't be integers.



{[30:'13',31:'14',32:'15']}

{["30":"13","31":"14","32":"15"]}

Bad: JavaScript object initializer, but a JavaScript array is not a valid property name. Also, JavaScript arrays are not

associative, and their initializers do not use object property syntax to specify their values.



[{"30":"13","31":"14","32":"15"}]

Good: An array initializer with a single element; that element is initialized as an object with properties named "30", "31", "32" and

values "13", "14", "15" (all strings).



"It took me a while to find the right JSON string format...."

You could have used json_encode() to do that :)

steve at weblite dot ca
24-Jan-2008 03:25


For JSON support in older versions of PHP you can use the Services_JSON class, available at http://pear.php.net/pepr/pepr-proposal-show.php?id=198



<?php

if ( !function_exists('json_decode') ){

    function json_decode($content, $assoc=false){

                require_once 'Services/JSON.php';

                if ( $assoc ){

                    $json = new Services_JSON(SERVICES_JSON_LOOSE_TYPE);

        } else {

                    $json = new Services_JSON;

                }

        return $json->decode($content);

    }

}



if ( !function_exists('json_encode') ){

    function json_encode($content){

                require_once 'Services/JSON.php';

                $json = new Services_JSON;

                

        return $json->encode($content);

    }

}

?>

yasarbayar at gmail dot com
26-Jul-2007 02:13


It took me a while to find the right JSON string format grabbed from mysql to be used in json_decode(). Here is what i came up with:



Bad(s) (return NULL):

{30:'13',31:'14',32:'15'}

{[30:'13',31:'14',32:'15']}

{["30":"13","31":"14","32":"15"]}



Good :

[{"30":"13","31":"14","32":"15"}]



returns:

array(1) { [0]=>  array(3) { [30]=>  string(2) "13" [31]=>  string(2) "14" [32]=>  string(2) "15" } }



hope this saves sometime..

AMA3
20-Jul-2007 06:02


phpben at hood dot id dot au wrote:

> AFAICT. The JSON docs seem to say that '"','/' and '\' must be quoted with a '\'



At first glance, it seems that way, but if you read the RFC (4627) carefully, forward-slash (/) *may* be escaped but need not be.  Specifically, Section 2.5 defines the following:



    string = quotation-mark *char quotation-mark

    char = unescaped / ... 

    unescaped = %x20-21 / %x23-5B / %x5D-10FFFF



Forward slash falls in the second range of unescaped characters, at %x2F.



It's strange that forward-slash is permitted to be escaped but not required to be, and that it has the same meaning either way, but that's how it's written, and so shall it be.



FMI: http://www.ietf.org/rfc/rfc4627.txt

phpben at hood dot id dot au
24-May-2007 07:43


whatifif at yahoo dot com said something about a bug:



"When I try to decode JSON string {"a":"<p>test</p>"} into array on server-side, it fails."



That is not a valid JSON string, AFAICT. The JSON docs seem to say that '"','/' and '\' must be quoted with a '\'



$ php -r 'echo json_encode("<p>test</p>");'

"<p>test<\/p>"



So it was your '/' character screwing it over.



You probably shouldn't blindly run stripslashes on your $input either! The only time you would is if magic_quotes_gpc is turned on and your string is coming from one of the GPC.



I inherited some PHP code which used Services_JSON. It stopped working when we upgraded PHP and started using this function. The problem was they ran html_entity_decode() over the input and &nbsp; was being turned into a character incompatible with UTF-8.

nospam (AT) hjcms (DOT) de
22-Apr-2007 09:15


You can't transport Objects or serialize Classes, json_* replace it bei stdClass!

<?php



$dom = new DomDocument( '1.0', 'utf-8' );

$body = $dom->appendChild( $dom->createElement( "body" ) );

$body->appendChild( $dom->createElement( "forward", "Hallo" ) );



$JSON_STRING = json_encode(

   array(

      "aArray" => range( "a", "z" ),

      "bArray" => range( 1, 50 ),

      "cArray" => range( 1, 50, 5 ),

      "String" => "Value",

      "stdClass" => $dom,

      "XML" => $dom->saveXML()

   )

);



unset( $dom );



$Search = "XML";

$MyStdClass = json_decode( $JSON_STRING );

// var_dump( "<pre>" , $MyStdClass , "</pre>" );



try {



   throw new Exception( "$Search isn't a Instance of 'stdClass' Class by json_decode()." );



   if ( $MyStdClass->$Search instanceof $MyStdClass )

      var_dump( "<pre>instanceof:" , $MyStdClass->$Search , "</pre>" );



} catch( Exception $ErrorHandle ) {



   echo $ErrorHandle->getMessage();



   if ( property_exists( $MyStdClass, $Search ) ) {

      $dom = new DomDocument( "1.0", "utf-8" );

      $dom->loadXML( $MyStdClass->$Search );

      $body = $dom->getElementsByTagName( "body" )->item(0);

      $body->appendChild( $dom->createElement( "rewind", "Nice" ) );

      var_dump( htmlentities( $dom->saveXML(), ENT_QUOTES, 'utf-8' ) );

   }

}



?>

paul at sfdio dot com
20-Jan-2007 07:08


I've written a javascript function to get around this functions limitations and the limitations imposed by IE's lack of native support for json serialization. Rather than converting variables to a json formatted string to transfer them to the server this function converts any javascript variable to a string serialized for use as POST or GET data.



String js2php(Mixed);



js2php({foo:true, bar:false, baz: {a:1, b:2, c:[1, 2, 3]}}));



will return:



foo=true&bar=false&baz[a]=1&baz[b]=2&baz[c][0]=1&...etc



function js2php(obj,path,new_path) {

  if (typeof(path) == 'undefined') var path=[];

  if (typeof(new_path) != 'undefined') path.push(new_path);

  var post_str = [];

  if (typeof(obj) == 'array' || typeof(obj) == 'object') {

    for (var n in obj) {

      post_str.push(js2php(obj[n],path,n));

    }

  }

  else if (typeof(obj) != 'function') {

    var base = path.shift();

    post_str.push(base + (path.length > 0 ? '[' + path.join('][') + ']' : '') + '=' + encodeURI(obj));

    path.unshift(base);

  }

  path.pop();

  return post_str.join('&');

}

Adrian Ziemkowski
13-Dec-2006 11:52


Beware when decoding JSON from JavaScript.  Almost nobody uses quotes for object property names and none of the major browsers require it, but this function does!   {a:1} will decode as NULL, whereas the ugly {"a":1} will decode correctly.   Luckily the browsers accept the specification-style quotes as well.

giunta dot gaetano at sea-aeroportimilano dot it
04-Sep-2006 08:16


Take care that json_decode() returns UTF8 encoded strings, whereas PHP normally works with iso-8859-1 characters.



If you expect to receive json data comprising characters outside the ascii range, be sure to use utf8_decode to convert them:



$php_vlaues = utf8_decode(json_decode($somedata))

giunta dot gaetano at sea-aeroportimilano dot it
04-Sep-2006 03:20


Please note that this function does NOT convert back to PHP values all strings resulting from a call to json-encode.



Since the json spec says that "A JSON text is a serialized object or array", this function will return NULL when decoding any json string that does not represent either an object or an array.



To successfully encode + decode single php values such as strings, booleans, integers or floats, you will have to wrap them in an array before converting them.

add a note

json_encode

JSON

Last updated: Sun, 25 Nov 2007