#16263 [Com]: session.start() create new empty session file and not resume existing session

From: Date: Mon, 05 Aug 2002 19:02:39 +0000
Subject: #16263 [Com]: session.start() create new empty session file and not resume existing session
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-16020@lists.php.net to get a copy of this message
ID: 16263 Comment by: zen_kermit@expn.com Reported By: kur@natur.cuni.cz Status: No Feedback Bug Type: Session related Operating System: Windows 2000 PHP Version: 4.1.2 New Comment: Just to add reinforcement to the cause: Using redhat 7.2, latest apache 1.3 version, php 4.2.2, in two servers (one with register_globals OFF and one with ON). The same problem occurs with both servers... Major pain.... Previous Comments: ------------------------------------------------------------------------ [2002-07-25 11:55:59] naintara@ndf.vsnl.net.in I now have PHP 4.2.3 - dev. My OS is Windows 2000 Professional Server. I am still getting a new session file. To better explain the scenario: I use session name and start the session at the top of the page/code. Strangely enough, the session values I gave immediately after the session_start() (which I did only for testing purposes) are retained in the new session file too. But values that I assign to some other session variables (which I actually need) are not. session_name("name"); session_start(); $_SESSION["v1"]="Hello"; $_SESSION["v2"]="WORLD"; /* lot of code, user authentication */ $_SESSION["username"]="whatever"; $_SESSION["username"] is not retained in the next page. On echoing the session id on the next page - I get a new id. Passing the session id in the URL made no difference. Adding global $HTTP_SESSION_VARS; made no difference. When I refresh the second page, miraculously, I get back the first session and the values. Even stranger, I get the v1 and v2 values ("Hello World") in both sessions. Lot of heartache involved because of this bug. A problem with sessions causes a lot of time loss and a lot of heart-ache. ------------------------------------------------------------------------ [2002-07-06 09:10:13] naintara@ndf.vsnl.net.in The bug exists in PHP 4.0.6 (it occurs infrequently) and it shows up in 4.2.1. At one point the session started behaving itself, but I installed 4.2.1 and it was gone, and when I re-installed 4.0.6, it's misbehaving again. It really is a nuisance. Machine running Windows 2000 Professional, IIS, PHP 4.2.1/PHP4.0.6 ------------------------------------------------------------------------ [2002-06-15 16:15:21] jason@insidemacgames.com This is happening to me in PHP 4.0.6, and right out of the blue at that. Some session code that has worked fine for a year and a half on several different machines and versions of PHP, etc. (including the current machine of course) just stopped working suddenly last night and is still broken after a restart of Apache and even a reboot. Machine is running Red Hat Linux 7.1, though via Red Hat Network all packages are upgraded to the latest Red Hat QAd versions (which is why I'm still at PHP 4.0.6). What is really bizarre is sessions continue to work on another part of my site but are failing on this set and a test set of pages I've just created as well. Absolutely nothing has changed; all of a sudden some of my session-using pages started to create blank session files (the cookie exists, the session file exists, there's nothing in it). ------------------------------------------------------------------------ [2002-05-16 00:00:04] php-bugs@lists.php.net No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". ------------------------------------------------------------------------ [2002-04-30 11:51:58] pryde@oldworld.de Problem still exist in 4.2.0 release, but appears to occur less often. I didn't try the fix yet since i use session_autostart, i guess i'll have to wait till this is fixed : ( ------------------------------------------------------------------------ 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/16263 -- Edit this bug report at http://bugs.php.net/?id=16263&edit=1

« previous php.bugs (#16020) next »