Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60923
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain analysisandsolutions.com designates 50.116.58.177 as permitted sender)
Date: Thu, 21 Jun 2012 10:12:41 -0400
To: Nikita Popov <nikita.ppv@googlemail.com>
Cc: PHP internals <internals@lists.php.net>
Message-ID: <20120621141241.GA25789@analysisandsolutions.com>
References: <CAF+90c-T9hPbuS3bUxnHw-+B+Y2VLu55wQJ8UrtzrcC7TiKyVw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAF+90c-T9hPbuS3bUxnHw-+B+Y2VLu55wQJ8UrtzrcC7TiKyVw@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [PHP-DEV] json_encode() behavior for incorrectly encoded strings
From: danielc@analysisandsolutions.com (Daniel Convissor)

Hi Nikita:

> PHP <= 5.3.13, PHP 5.4, master behave as follows when an invalid UTF-8
> string is encountered:
>  * A warning is thrown, but only if display_errors=off

So the warning is put into the error log?  But only if display_errors is
off?  And if display_errors is on, no warning is produced?

That's very counter-intuitive and un-PHP-like.  Someone mentioned it's for
security reasons.  By that logic, we should get rid of all error
messages because they all reveal some information that can be used by
attackers.

Thanks,

--Dan

-- 
 T H E   A N A L Y S I S   A N D   S O L U T I O N S   C O M P A N Y
            data intensive web and database programming
                http://www.AnalysisAndSolutions.com/
        4015 7th Ave #4, Brooklyn NY 11232  v: 718-854-0335