Edit report at https://bugs.php.net/bug.php?id=49366&edit=1

 ID:                 49366
 Comment by:         dtremblay dot fafard at gmail dot com
 Reported by:        don at smugmug dot com
 Summary:            Make slash escaping optional in json_encode()
 Status:             Closed
 Type:               Feature/Change Request
 Package:            JSON related
 Operating System:   CentOS 5.3
 PHP Version:        5.3.0
 Assigned To:        aharvey
 Block user comment: N
 Private report:     N

 New Comment:

Actually, I can't find any reason why is escaping slashes by default and create 
an option to remove this feature.  Usually, when you want something added (e.g. 
Escaping Slashes), you use an option to recreate the feature wanted. So why is 
the option used to REMOVE a feature? Options exists to add features, not remove 
them?? Where am I wrong?


Previous Comments:
------------------------------------------------------------------------
[2010-09-16 15:53:38] ahar...@php.net

This bug has been fixed in SVN.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
 
Thank you for the report, and for helping us make PHP better.

I've implemented this on trunk via a json_encode() option called 
JSON_UNESCAPED_SLASHES. The default behaviour remains to escape slashes.

------------------------------------------------------------------------
[2010-09-16 15:53:29] ahar...@php.net

Automatic comment from SVN on behalf of aharvey
Revision: http://svn.php.net/viewvc/?view=revision&revision=303421
Log: Implemented FR #49366 (Make slash escaping optional in json_encode()).

------------------------------------------------------------------------
[2010-08-08 14:43:22] jd2 at dilltree dot com

Totally agree.  This is needed for anything such as a REST service that wants 
to 
return JSON with valid urls.

------------------------------------------------------------------------
[2009-10-21 21:14:40] jemptymethod at acm dot org

I concur with the suggested course of action making the escaping of slashes 
controllable with a flag as I'm experiencing the same issue as the OP albeit on 
Debian (rather than CentOS)

------------------------------------------------------------------------
[2009-08-26 08:50:11] j...@php.net

It's not incorrect to escape slashes. It's also suggested on the RFC to do so. 
Just look at the chart on http://www.json.org/ for string..

But since it isn't wrong either NOT to escape them, I'll just reclassify this. 
We can add another option to that optional bitmask "options". 

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    https://bugs.php.net/bug.php?id=49366


-- 
Edit this bug report at https://bugs.php.net/bug.php?id=49366&edit=1

Reply via email to