Re: json_encode() behavior for incorrectly encoded strings
| From: | Ferenc Kovacs | Date: | Sat, 23 Jun 2012 20:34:26 +0000 |
| Subject: | Re: json_encode() behavior for incorrectly encoded strings | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-60948@lists.php.net to get a copy of this message | ||
On Sat, Jun 23, 2012 at 9:53 PM, Stas Malyshev <smalyshev@sugarcrm.com>wrote:
> Hi!
>
> > The warning for invalid UTF-8 stays intact and is thrown also with
> > display_errors = On. If this behavior is undesired this can be remedied
> > later.
>
> Must we discuss it 1000 times anew? There was a reason why it didn't
> throw warning when display_errors is on. The reason is that it is very
> easy to feed the server configured with display_errors = on wrong JSON
> and thus force it to reveal information, and this is largely beyond the
> control of application writer.
>
> But what I am worried about even more is getting back to that "commit
> first, discuss later" mentality. Why we have again a commit in the
> stable branch before we have a consensus decision what it should be doing?
>
from the side, it doesn't seems to be a consensus about having this
exception not honoring the display_errors setting.
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu