Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66876
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.173 as permitted sender)
Message-ID: <5158AA5F.2050305@gmail.com>
Date: Sun, 31 Mar 2013 23:27:59 +0200
User-Agent: Thunderbird
MIME-Version: 1.0
To: ALeX <lists.php@tx0.eu>
CC: PHP Internals <internals@lists.php.net>
References: <5157A55A.1070507@sugarcrm.com> <CAAyV7nGtz94NaFdeQ4KL9X3_LX-dc=zbt35o=qoqd1zWGTFgaA@mail.gmail.com> <CAL+t6cF_pzrQtNSYMjCmxhm67QtbfhpEUiWx4xGWxAJpafrwkQ@mail.gmail.com> <5157AD1D.3020606@sugarcrm.com> <5158847D.4080806@mrclay.org> <CAFFuhJpUbDN9ufdfV_TZbV-YZ9XU+mhuGZ-KwOSkgooNFiNgNg@mail.gmail.com>
In-Reply-To: <CAFFuhJpUbDN9ufdfV_TZbV-YZ9XU+mhuGZ-KwOSkgooNFiNgNg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: [lists.php] Re: [PHP-DEV] [RFC] more secure unserialize()
From: keisial@gmail.com (=?UTF-8?B?w4FuZ2VsIEdvbnrDoWxleg==?=)

On 31/03/13 23:18, ALeX wrote:
>> JSON and serialize() are (inherently) different serialization formats with different use-cases [...]
> Yes, and json requires that all strings (including the keys) has to be
> valid utf-8, and I'm sure that's not always the case (serialize can
> use binary data in both places).

Yes, it is a problem.
> var_dump(json_encode("\xe1 - \xc3\xa1"));
> PHP Warning:  json_encode(): Invalid UTF-8 sequence in argument in php
> shell code on line 1
> string(4) "null"
In a perfect world, all your input is utf-8, but sometimes what you get
is in a different encoding...
(and you still want to store it as-it-came in the first layer)