Zend Framework

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.10.6
• Fix Version/s: 1.10.7
• Component/s: Zend_Session
• Labels:

  None

If we have namespace with expirationSeconds setted to 1, and expirationHops to 100, the notice will be produced by _processStartupMetadataGlobal method at Zend/Session.php on line 536. (Expiration values can be more realistic, but I took them for the faster problem detection.)

See the code below:

{{
foreach ($_SESSION['__ZF'] as $namespace => $namespace_metadata) {

// Expire Namespace by Time (ENT)
if (isset($namespace_metadata['ENT']) && ($namespace_metadata['ENT'] > 0) && (time() > $namespace_metadata['ENT']) ) { unset($_SESSION[$namespace]); unset($_SESSION['__ZF'][$namespace]); }

// Expire Namespace by Global Hop (ENGH)
if (isset($namespace_metadata['ENGH']) && $namespace_metadata['ENGH'] >= 1) {
$_SESSION['__ZF'][$namespace]['ENGH']--;

if ($_SESSION['__ZF'][$namespace]['ENGH'] === 0) {
if (isset($_SESSION[$namespace])) { parent::$_expiringData[$namespace] = $_SESSION[$namespace]; unset($_SESSION[$namespace]); }
unset($_SESSION['__ZF'][$namespace]);
}
}
}}

In the '// Expire Namespace by Time (ENT)' namespace can be unsetted from the $_SESSION, but $namespace_metadata is left without changes.
So the second block '// Expire Namespace by Global Hop (ENGH)' will try to execute same logic as in previous, but the Notice will be generated on the line: $_SESSION['__ZF'][$namespace]['ENGH']--; because $_SESSION variable has no longer the $namespace key.

• Assignee:

  Ralph Schindler

  Reporter:

  Vova Yatsyuk

• Created:

  15/Jul/10 3:54 AM

  Updated:

  16/Jul/10 1:22 PM

  Resolved:

  16/Jul/10 1:22 PM