ID: 16282
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Feedback
+Status: No Feedback
Bug Type: Session related
Operating System: Linux 2.4.7-10
PHP Version: 4.0.6
New Comment:
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".
Previous Comments:
------------------------------------------------------------------------
[2002-03-26 05:12:29] [EMAIL PROTECTED]
Please try php-4.2.0rc1.tar.gz from www.php.net/~derick
Derick
------------------------------------------------------------------------
[2002-03-26 05:04:39] [EMAIL PROTECTED]
<?php
session_start();
session_register ("count");
header ("Expires: Mon, 26 Jul 1997 05:00:00 GMT");
$count++;
//session_write_close();
?>
If I don't put the session_write_close() call, I will end up getting an
empty session file, and all the session data is lost.
Putting the call solves the problem, but this shouldn't happen at all.
Using Apache 1.3.22 with PHP 4.0.6 as a dynamic module.
---------------
session info as read from phpinfo()
----------------
session.auto_start Off Off
session.cache_expire 180 180
session.cache_limiter nocache nocache
session.cookie_domain no value no value
session.cookie_lifetime 0 0
session.cookie_path / /
session.cookie_secure Off Off
session.entropy_file no value no value
session.entropy_length 0 0
session.gc_maxlifetime 1440 1440
session.gc_probability 1 1
session.name PHPSESSID PHPSESSID
session.referer_check no value no value
session.save_handler files files
session.save_path /tmp /tmp
session.serialize_handler php php
session.use_cookies On On
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=16282&edit=1
