ID: 43308
Comment by: emil dot hall at gamereactor dot se
Reported By: jani dot ollikainen at pronetko dot fi
Status: Open
Bug Type: Feature/Change Request
Operating System: Linux
PHP Version: 5.2.5
New Comment:
You get one vote from me! This is far from bogus. And here is a simple
test case:
session_start();
echo serialize($_SESSION), "\n";
echo file_get_contents('/path/sess_'.session_id());
If the advice from [email protected] was solid, I would expect the exact
same output from both echoes.
Actual result:
a:1:{s:4:"asdf";s:6:"foobar";}
asdf|s:6:"foobar";
Previous Comments:
------------------------------------------------------------------------
[2007-11-15 22:29:11] jani dot ollikainen at pronetko dot fi
Description:
------------
Ok, Tried this once with feature request #42725
and no go. Second try..
First read the #42725 and then read this:
Of course I know those, but those don't unserialize() data which is
formatted like:
PUTLASTHOST|s:23:"kuvajainen.domain.tld";PUTHOST|s:23:"kuvajainen.domain.tld";PUTDOCROOT|s:39:"/data/www/c/k/u/kuvajainen.domain.tld";putprofiles|s:3:"4,5";
And there are many different serializer handlers in php, for example:
Registered serializer handlers => php php_binary wddx
So there should be functions which can use those registered serializer
handlers to serialize/unserialize data accordingly selected serializer
handler.
So I don't think that this is bogus feature request.
Prove me wrong, but serialize/unserialize isn't the answer.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=43308&edit=1