Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81676
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.177 as permitted sender)
MIME-Version: 1.0
Date: Mon, 2 Feb 2015 20:57:28 -0500
Message-ID: <CA+sv8zC==OeU9nnzxM=65A24fV+WiTdhbJgqLg-u=wVhGtL9Zw@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1134be8ca8123f050e25641c
Subject: Serialize generating corrupted data
From: jrbasso@gmail.com (Juan Basso)

--001a1134be8ca8123f050e25641c
Content-Type: text/plain; charset=UTF-8

Hi,

I was testing few things today and I released one bug in the serialize
function. The serialize function returns a corrupted value when it is
serializing an object that contains a __sleep magic method and this method
return some key that are not string. Ie:

http://viper-7.com/EK16EV

If the __sleep returns a string that is not a property it is fine, it will
give the notice and the generated response is a valid serialized data (in
another words you can use unserialize to retrieve the object back). Ie,
http://viper-7.com/H9ooff

I can try to make a patch to solve it, but before that I would like how the
behavior should be. Some options:
1) Give the notice saying the field doesn't exist and do not include on the
serialized response
2) Give the notice saying the field doesn't exist and convert the value to
string (ie, on my example the int(1) would be transformed to string(1))
3) Give a warning and return false once the input from __sleep is invalid
4) None of the above alternative
5) Don't change it


Thanks,
Juan Basso

--001a1134be8ca8123f050e25641c--