<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>Session list provides unserialize error</title> 
  <pubDate>Fri, 10 Apr 2026 07:03:45 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/3586</link> 
  <atom:link rel="self" type="application/rss+xml" title="Session list provides unserialize error" href="https://bugs.horde.org/ticket/3586/rss" /> 
  <description>Session list provides unserialize error</description> 
 
   
   
  <item> 
   <title>I seem to be getting a few of these on about 1/3 of the sess</title> 
   <description>I seem to be getting a few of these on about 1/3 of the sessions active.  I&#039;d imagine there&#039;s some character not being escaped properly in the session? 



Notice: unserialize(): Error at offset 93 of 130 bytes in /var/www/horde/lib/Horde/SessionHandler.php on line 217



Notice: unserialize(): Error at offset 92 of 121 bytes in /var/www/horde/lib/Horde/SessionHandler.php on line 217



Notice: unserialize(): Error at offset 93 of 130 bytes in /var/www/horde/lib/Horde/SessionHandler.php on line 217



Notice: unserialize(): Error at offset 92 of 121 bytes in /var/www/horde/lib/Horde/SessionHandler.php on line 217</description> 
   <pubDate>Wed, 08 Mar 2006 21:03:49 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/3586#t17420</link> 
  </item> 
   
  <item> 
   <title>a:8:{s:13:&quot;authenticated&quot;;b:1;s:6:&quot;userId&quot;;s:20:&quot;email@domai</title> 
   <description>a:8:{s:13:&quot;authenticated&quot;;b:1;s:6:&quot;userId&quot;;s:20:&quot;email@domain.com&quot;;s:11:&quot;credentials&quot;;s:40:&quot;ùªaA 34°? ñd 36¸ì¸õÇÁÂ???¼



And then the input string just stops.  The session file keeps going, but the string it is unserializing ( $vars[$auth+1] ) fails to be complete, and hence fails on the unserializing as it just stops.</description> 
   <pubDate>Wed, 08 Mar 2006 21:18:10 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/3586#t17421</link> 
  </item> 
   
  <item> 
   <title>What&#039;s the complete string before the split in this case ($s</title> 
   <description>What&#039;s the complete string before the split in this case ($session_data)? If it&#039;s too large, it might sufficient to provide only the characters of the &quot;credential&quot; string.</description> 
   <pubDate>Fri, 10 Mar 2006 00:07:12 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/3586#t17476</link> 
  </item> 
   
  <item> 
   <title>See attached (intended to preserve the non-ASCII characters)</title> 
   <description>See attached (intended to preserve the non-ASCII characters).



You&#039;ll notice I took a printout of $vars[$auth+1] and then the first section of the $session_data variable which should show you the characters leading up to it that are getting misparsed.  This was probably similar to the case earlier (forgot to save the session before), and causes the same problem.  At this point it&#039;s character 90 of the unserialize



&quot;Notice: unserialize(): Error at offset 90 of 131 bytes in /var/www/horde/lib/Horde/SessionHandler.php on line 217&quot;</description> 
   <pubDate>Mon, 13 Mar 2006 16:34:47 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/3586#t17684</link> 
  </item> 
   
  <item> 
   <title>The data is what I expected. The encrypted credential data c</title> 
   <description>The data is what I expected. The encrypted credential data contains a pipe character that breaks our preg_split()&#039;ing.</description> 
   <pubDate>Mon, 13 Mar 2006 16:51:35 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/3586#t17685</link> 
  </item> 
   
  <item> 
   <title>Fixed in CVS.</title> 
   <description>Fixed in CVS.</description> 
   <pubDate>Thu, 13 Jul 2006 23:32:04 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/3586#t21976</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
