ID: 34588
Updated by: [EMAIL PROTECTED]
Reported By: michael dot caplan at htc dot ca
-Status: Verified
+Status: Closed
Bug Type: Documentation problem
Operating System: Irrelevant
PHP Version: Irrelevant
New Comment:
This bug has been fixed in the documentation's XML sources. Since the
online and downloadable versions of the documentation need some time
to get updated, we would like to ask you to be a bit patient.
Thank you for the report, and for helping us make our documentation
better.
"If different scripts have different values of session.gc_maxlifetime
but shares the same place for storing the session data then the script
with the minimum value will be cleaning the data. In this case, use
this directive together with session.save_path."
Previous Comments:
------------------------------------------------------------------------
[2005-09-23 16:03:44] michael dot caplan at htc dot ca
Okay. Thanks again!
------------------------------------------------------------------------
[2005-09-23 16:02:39] [EMAIL PROTECTED]
Changing status to verified.
------------------------------------------------------------------------
[2005-09-23 15:59:02] [EMAIL PROTECTED]
We'll just leave it as a documentation issue. You *can* isolate the
session files between different instances by simply changing (for
example) the location of the session files using session.save_path in
your .htaccess file, or by writing your own custom handler.
------------------------------------------------------------------------
[2005-09-23 14:54:18] michael dot caplan at htc dot ca
Now that makes perfect sense! Should this be considered just a
documentation issue, or should PHP file based session support add an
additional feature to distinguish sessions from different hosts?
Thanks. Sorry for the bogus bug report.
------------------------------------------------------------------------
[2005-09-23 00:24:01] [EMAIL PROTECTED]
You mention that you have change session.gc_max_lifetime in an
.htaccess file. Does this mean that there are other areas of your site
/ other virtual hosts on the same machine that also use sessions? If
that's the case, it might be that the other instances are in fact
performing garbage collection because they take the master value from
php.ini--I don't think the session handler is capable of telling
whether a particular session file was created by a given instance of
the interpreter or not, and just cleans out everything it thinks has
expired.
------------------------------------------------------------------------
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/34588
--
Edit this bug report at http://bugs.php.net/?id=34588&edit=1
