On Sat, Jun 23, 2012 at 9:53 PM, Stas Malyshev <smalys...@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
