#17512 [Com]: $_SESSION support may be inconsistent

ID: 17512 Comment by: mclinden@informed.net Reported By: dan@abledesign.com Status: Analyzed Bug Type: Session related Operating System: ANY PHP Version: 4.3.0-dev New Comment: Just tried the script from mfischer dated 30 May 2002 on the current CVS of 4.3-dev and got some interesting results. First, keys were stored but not the values. Second, when the key was a number, any subsequent entry of key-value pairs would overwrite the numeric key although subsequent alphabetic keys would continue to accumulate (still without the values). Previous Comments: ------------------------------------------------------------------------ [2002-08-07 03:06:27] yohgaki@php.net Session work mostly, but the problem original reporter reported do exist. We need to fix the way session vars are stored to close this one. (Unless I'm missing the fix ;) ------------------------------------------------------------------------ [2002-08-05 15:12:46] zen_kermit@expn.com This problem is smattered all over these bug forums. Will someone from PHP please address is it as an actual issue? It has effectivley mangled a few of my websites. ------------------------------------------------------------------------ [2002-06-12 05:32:16] info@virogo.com Same in NT4 / IIS4. No consistent registering possible... It writes 2 ses_3237234748 bla bla, one of them is 0 bytes. The other contains the sessiondata. But when trying to read out the sessiondata thru $_SESSION, it seems to be empty. ------------------------------------------------------------------------ [2002-05-30 18:47:09] dan@abledesign.com > Given your response to my sample tells > me that sessions do work properly. The point of the report was not to say that sessions do not work (they obviously do, as shown by the fix I outlined above), rather that certain aspects of them do not appear to be properly supported in some environments. > I suspect a bug in the code you use or > the way you expect sessions to work. Ok, here is what I've got, in simplified form (no need for you to read through the extraneous hidden fields, MySQL queries, and what not): -- login form: print <<<HERE <form action="$PHP_SELF" method="GET"> <input type="text" name="username" value="" size="20" maxlength="15"> <input type="password" name="password" value="" size="20" maxlength="15"> <input type="submit" value="Submit"> </form> HERE; -- login processing script: (This is actually routed through an index page that starts the session, includes config and library files, page formatting, and includes the requested file, which is the login processing form in this case.) <?php session_start(); if (isset($_SESSION["sess_id"])) { // remove any existing sessions for this user unset($_SESSION["sess_id"]); unset($_SESSION["sess_name"]); } $sql = "SELECT * FROM Users WHERE Username='". addslashes($_GET["username"]) ."' AND Password='". addslashes($_GET["password"]) ."'"; $result = mysql_query($sql); if (!$result || (mysql_num_rows($result) < 1)) { // redirect to failed login prompt } else { $row = mysql_fetch_array($result); $_SESSION["sess_id"] = $row["ID"]; $_SESSION["sess_name"] = $_GET["username"]; // redirect to main page after setting the session echo "<script language=\"JavaScript\">window.location='index.php'</script>"; } ?> As explained above, that does not work on all servers. Doing the exact same thing but with $HTTP_SESSION_VARS in place of $_SESSION and not using unset() on the session variables does however work. Surely I'm not misunderstanding how sessions should work in this example? Thanks, Dan ------------------------------------------------------------------------ [2002-05-30 18:06:03] mfischer@php.net Given your response to my sample tells me that sessions do work properly. I suspect a bug in the code you use or the way you expect sessions to work. Try to cut it down to a simple, self-contained example what you're trying to archive. ------------------------------------------------------------------------ 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/17512 -- Edit this bug report at http://bugs.php.net/?id=17512&edit=1