Why does `json_encode` add unwanted backslashes to my JSON output?

JSON Conundrum: Unraveling Backslash Anomalies in json_encode

In the realm of JSON data encoding, the json_encode function has long been a trusted tool. However, recent encounters have stirred up a puzzling question: why is json_encode adding unwanted backslashes?

To delve into this enigma, let's examine the code provided:

print_r($result);
echo json_encode($result);

The print_r command displays the associative array as expected. When json_encode is applied, it converts the array into JSON, which appears valid. However, upon further inspection, hidden slashes emerge.

{
    "logo_url":"http:\/\/mysite.com\/uploads\/gallery\/7f\/3b\/f65ab8165d_logo.jpeg",
    "img_id":"54",
    "feedback":{"message":"File uploaded","success":true}
}

Why these extraneous backslashes? Further debugging reveals a twist in the tale. The anomaly occurs not in json_encode itself, but in the subsequent parseJSON call. Examining the JavaScript data using data.toSource() uncovers a non-JSON-compliant string:

({response:"{\"logo_url\":\"http:\/\/storelocator.com\/wp-content\/uploads\/gallery\/7f\/3b\/71b9520cfc91a90afbdbbfc9d2b2239b_logo.jpeg\",\"img_id\":\"62\",\"feedback\":{\"message\":\"File uploaded\",\"success\":true}}", status:200})

The Solution:

The key to resolving this issue lies in specifying the "JSON_UNESCAPED_SLASHES" option to json_encode. Introduced in PHP version 5.4, this option effectively prevents the function from adding backslashes to forward slashes.

json_encode($array,JSON_UNESCAPED_SLASHES);

Armed with this knowledge, the mystery of the unwanted backslashes is solved, enabling seamless JSON encoding without the escapist interferences!

The above is the detailed content of Why does `json_encode` add unwanted backslashes to my JSON output?. For more information, please follow other related articles on the PHP Chinese website!