1

I'm trying to debug some old code from CodeIgniter 2.2. When running some data thru Session, I noticed an unserialize error, Message: unserialize(): Error at offset 160 of 163 bytes. After doing some debugging and research, I found out it's a common backslash issue when unserializing data from Sessions.

The serialized data I'm using has objects of data with backslashes in them, which causes the errors to occur. I'm in need of a replacement that can handle standard class objects as well.

Could someone recommend a quick replacement for codeigniter's Session _serialize() and _unserialize() methods?

public function data_test() {

    $input = array(
        (object)array('name' => 'test2', 'desc' => 'bla bla ob/gyn'),
        (object)array('name' => 'test2', 'desc' => 'bla bla ob\\gyn'),
    );
    var_dump($input);

    $data = $this->_serialize($input);
    var_dump($data);

    $result = $this->_unserialize($data);
    var_dump($result);


}



// --------------------------------------------------------------------

/**
 * Serialize an array
 *
 * This function first converts any slashes found in the array to a temporary
 * marker, so when it gets unserialized the slashes will be preserved
 *
 * @access  private
 * @param   array
 * @return  string
 */
function _serialize($data) {
    if (is_array($data)) {
        foreach ($data as $key => $val) {
            if (is_string($val)) {
                $data[$key] = str_replace('\\', '{{slash}}', $val);
            }
        }
    } else {
        if (is_string($data)) {
            $data = str_replace('\\', '{{slash}}', $data);
        }
    }

    return serialize($data);
}

// --------------------------------------------------------------------

/**
 * Unserialize
 *
 * This function unserializes a data string, then converts any
 * temporary slash markers back to actual slashes
 *
 * @access  private
 * @param   array
 * @return  string
 */
function _unserialize($data) {

    $data = unserialize(strip_slashes($data));

    if (is_array($data)) {
        foreach ($data as $key => $val) {
            if (is_string($val)) {
                $data[$key] = str_replace('{{slash}}', '\\', $val);
            }
        }

        return $data;
    }

    return (is_string($data)) ? str_replace('{{slash}}', '\\', $data) : $data;
}
jjwdesign
  • 3,272
  • 8
  • 41
  • 66
  • I've seen that base64_encode(serialize($data)) to serialize and unserialize(base64_decode($data)) to unserialize seem to process the data without errors. Does anyone recommend this approach? – jjwdesign Jun 26 '15 at 23:18
  • Yes, Its fine approach. you can have look [here](http://stackoverflow.com/questions/2888418/unserialize-problem-in-php) – jagad89 Jun 27 '15 at 03:23
  • The same question asked in earlier in stack over flow [Follow this][1] [1]: http://stackoverflow.com/questions/10152904/unserialize-function-unserialize-error-at-offset – Nithin Krishnan P Jun 27 '15 at 05:15

2 Answers2

2
/**
 * Serialize an array
 *
 * This function serializes the data and then base64_encodes it for 
 * storage with memcached. This avoids the common backslash issue.
 *
 * @access  private
 * @param   array
 * @return  string
 */
function _serialize($data) {
    return base64_encode(serialize($data));
}

// --------------------------------------------------------------------

/**
 * Unserialize
 *
 * This function unserializes a data string. I first base64_decodes
 * the data from memcached storage.
 */
function _unserialize($data) {
    return unserialize(base64_decode($data));
}
jjwdesign
  • 3,272
  • 8
  • 41
  • 66
0

You can sometimes come across this issue if you are using different versions of PHP, or if you change the version of PHP you are using while a session was open.

For example if you have a session cookie with an app that uses PHP 5.6.* and then you try to use it with an app (that resides on another sub-domain) that uses PHP 7.2.*, then you are going to get a warning error. Or, if you had an open session and then you changed the version of PHP that you are using with your app (say if you are developing locally and switching around PHP versions), then you'll get the warning. So best to use serialize/unserialize and with PHP version that does not change.

csautot
  • 36
  • 6