ID: 20449 Comment by: josh at bauguss dot net Reported By: josh at zebotech dot com Status: No Feedback Bug Type: Session related Operating System: redhat 7.3 PHP Version: 4.3.0-dev New Comment:
I just got the last comment sent to me in my email so I rechecked this bug. I'm suprised to see that most of the comments that I had posted to this bug are now gone. I'm also really suprised that this bug report had been suspended. Just for the last guys benefit for his comment on this bug... I wrote my own session handling routine and that completely fixed the problem. I now don't use any of the session calls built into php. I also wrote my own serialize/deserialize function. While I can't prove it at the moment as I don't have time to, I'm pretty sure that the problem with the session handler is with the serialize/deserialize routine used by the session handler. I seem to remember this being my conclusion way back over a year ago and I think I even provided comments in this bug report that seem to no longer be attached to this bug. I can't recall at the moment nor can I risk testing it on my site, but I think when I tried using the serialize/deserialize function in php in my own session manager I ran into the same symptoms of this bug. When I wrote my own routine, it disappeared and solved my session management woes. Hope that helps. Josh Bauguss Previous Comments: ------------------------------------------------------------------------ [2004-01-16 15:30:26] dspice at samys dot com I was extremely relieved to find this post, as I've been having the identical problem. However, it seems like it's not yet resolved in any practical manner. The same scenario occurs for me: a small but important number of users lose the data in the session arrays (but not the session itself) - I believe when the protocol switches from http to https. I have tried many times on many machines to replicate it; so far of the customers I have been able to get data from, it seems they are all running IE6 on Windows XP, but that could easily just be statistical probability. I've tried to replicate the problem using the exact same IE version number, with no success. I can't tell how many people this is affecting, exactly, but I can tell that it's costing us money. It's reassuring to see other people facing the same problem, but disparaging to see that it's been over a year and this apparent bug still has not been resolved. Any help would be greatly appreciated. ------------------------------------------------------------------------ [2003-06-09 08:44:10] [EMAIL PROTECTED] No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you. ------------------------------------------------------------------------ [2003-06-02 17:09:32] [EMAIL PROTECTED] This should be fixed in PHP 4.3.2, so please give it a try. ------------------------------------------------------------------------ [2003-05-09 00:18:19] php dot bugs dot krishaven at spamgourmet dot com My session problems appear to all be caused by the fact that $array1=$array2 doesn't do a "deep copy" as described in bugs: http://bugs.php.net/bug.php?id=8130 http://bugs.php.net/bug.php?id=21288 http://bugs.php.net/bug.php?id=20993 Personally, I don't think that the previous dismissal of the problem with "This will not be fixed anytime soon. It is a deep seated problem in the implementation and fixing it would cause speed problems and numerous other problems," or considering it a documentation problem are appropriate responses. I guess I was lucky that this was causing an apache segfault, or who knows how much data this could have corrupted? ------------------------------------------------------------------------ [2002-11-21 15:29:24] russ at zerotech dot net NULL ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/20449 -- Edit this bug report at http://bugs.php.net/?id=20449&edit=1
