Ticket #43 (assigned defect)

Opened 2 years ago

Last modified 2 years ago

eaccelerator messes up horde sessions

Reported by: anonymous Assigned to: hans (accepted)
Priority: major Milestone: 1.0
Component: eAccelerator Version: 0.9.5
Keywords: Cc: dave@openlab.nl

Description

Looks to me sessions get pretty messed up.

When eaccelerator is enabled errors start popping up. The offending code line: 

$cache[$key][$mailbox] = $_SESSION['imp']['namespace'][''];

My guess is the session support doesn't handle multi dimension session arrays.

Investigation continues...

Change History

04/06/06 19:11:27 changed by hans

Do you have some more information already? Could you please be more specific as to what errors are being reported etc.?

Thanks

04/10/06 10:06:50 changed by dave@openlab.nl

I disabled EA because of this bug. When looking at the error values it looked like the wrong memory adresses where used. Because the session variables contained "strange" values (UTF8 strings and strings available in the running script).

04/19/06 00:18:42 changed by james.couzens@electricmail.com

What version of horde? I was going to try 0.9.5 but that won't fly if it monkies up horde sessions.

04/19/06 08:32:50 changed by dave@openlab.nl

I believe it's all recent versions. Because of Horde's huge objects, all accelerator's seem to have some problems with it.

Perhaps I need to include some information about my setup: Apache 2.0.55 PHP 5.1.2 (apache module) Horde 3.1 (same problems with 3.1.1) with IMP 4.1 (same problems with 4.1.1)

05/26/06 19:11:44 changed by hans

  • owner changed from somebody to hans.
  • priority changed from critical to major.
  • status changed from new to assigned.

As the original reporter already guessed, it is related to the registering of arrays in sessions. The eA session handler needs a serializer to handle this data properly. It is something that needs to be worked on.

06/30/06 16:17:54 changed by bart

  • milestone set to 1.0.

09/18/06 07:48:06 changed by Sam Bauers

Can someone confirm if this issue affects all use of arrays in sessions. So far my testing in another application (not Horde) with arrays in sessions has worked fine. Perhaps it specifically has to do with the offending line posted in the original report. Specifically I'm looking at that empty string in the last node of the session array and thinking it is a bit non-standard.