php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Request #76681 Make unserialize() handle a new "callback" option entry
Submitted: 2018-07-30 08:46 UTC Modified: 2018-07-31 21:08 UTC
Votes:3
Avg. Score:4.3 ± 0.5
Reproduced:2 of 2 (100.0%)
Same Version:1 (50.0%)
Same OS:1 (50.0%)
From: nicolas dot grekas+php at gmail dot com Assigned:
Status: Open Package: Scripting Engine problem
PHP Version: Next Minor Version OS:
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!
Your email address:
MUST BE VALID
Solve the problem:
30 - 3 = ?
Subscribe to this entry?

 
 [2018-07-30 08:46 UTC] nicolas dot grekas+php at gmail dot com
Description:
------------
Right now, the unserialize callback must be defined using an ini setting.
It would be more convenient to be able to set it via new option.
(This could potentially also allow setting it to a Closure?)

BEFORE:
$unserializeCallbackHandler = ini_set('unserialize_callback_func', 'my_unserialize_callback');
try {
    unserialize($value);
} finally {
    ini_set('unserialize_callback_func', $unserializeCallbackHandler);
}

AFTER:
unserialize($value, ['callback' => 'my_unserialize_callback']);



Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2018-07-31 21:08 UTC] cmb@php.net
I think that needs to be discussed on internals@ (and might even
need an RFC).  Nicolas?
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Tue Apr 23 20:01:29 2024 UTC