Tickets :: [#3586] Session list provides unserialize error

6.0.0-beta1

7/7/25

Summary	Session list provides unserialize error
Queue	Horde Framework Packages
Queue Version	HEAD
Type	Bug
State	Resolved
Priority	1. Low
Owners	Horde Developers (at)
Requester	phyre (at) rogers (dot) com
Created	03/08/2006 (7061 days ago)
Due
Updated	07/13/2006 (6934 days ago)
Assigned	03/13/2006 (7056 days ago)
Resolved	07/13/2006 (6934 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

07/13/2006 11:32:04 PM	Jan Schneider	Comment #6 State ⇒ Resolved	Reply to this comment
Fixed in CVS.

05/22/2006 08:12:52 AM	Jan Schneider	Version ⇒ HEAD Queue ⇒ Horde Framework Packages

03/13/2006 04:51:35 PM	Jan Schneider	Comment #5 Assigned to Horde Developers State ⇒ Assigned	Reply to this comment
The data is what I expected. The encrypted credential data contains a pipe character that breaks our preg_split()'ing.

03/13/2006 04:34:47 PM	phyre (at) rogers (dot) com	Comment #4 New Attachment: ttt	Reply to this comment
See attached (intended to preserve the non-ASCII characters). You'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's character 90 of the unserialize "Notice: unserialize(): Error at offset 90 of 131 bytes in /var/www/horde/lib/Horde/SessionHandler.php on line 217"

03/10/2006 12:07:12 AM	Jan Schneider	Comment #3 State ⇒ Feedback	Reply to this comment
What's the complete string before the split in this case ($session_data)? If it's too large, it might sufficient to provide only the characters of the "credential" string.

03/08/2006 09:18:10 PM	phyre (at) rogers (dot) com	Comment #2	Reply to this comment
a:8:{s:13:"authenticated";b:1;s:6:"userId";s:20:"email@domain.com";s:11:"credentials";s:40:"ùªaA34°? ñd36¸ì¸õÇÁÂ???¼ 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.

03/08/2006 09:03:49 PM	phyre (at) rogers (dot) com	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Session list provides unserialize error Queue ⇒ Horde Base State ⇒ Unconfirmed	Reply to this comment
I seem to be getting a few of these on about 1/3 of the sessions active. I'd imagine there'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