Re: Bug #12915 Updated: session_write_close() has to be called explicitly
| From: | Yasuo Ohgaki | Date: | Thu, 13 Dec 2001 12:01:46 +0000 |
| Subject: | Re: Bug #12915 Updated: session_write_close() has to be called explicitly | ||
| References: | 1 2 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-73550@lists.php.net to get a copy of this message | ||
To me, this bug report is most likely a user error.
(Bug in user session handler)
Bogus may be the best status for now.
I like Status = No Feedback, too ;)
But it's not there.
--
Yasuo Ohgaki
sander@php.net wrote:
ID: 12915 Updated by: sander Reported By: ggabor@sopron.hu Old Status: Feedback Status: Closed Bug Type: Session related Operating System: Linux 2.4.9 (Debian woody) PHP Version: 4.0.6 New Comment: No feedback. Closing. Previous Comments: ------------------------------------------------------------------------ [2001-11-18 01:27:22] sebastian@php.net Does this problem persist with the current release candidate for PHP 4.1.0? It can be found at http://www.php.net/~zeev/php-4.1.0RC2.tar.gz. ------------------------------------------------------------------------ [2001-08-22 21:04:44] ggabor@sopron.hu Sessions work correctly if session.save_handler is set to 'files', but if I set it to 'user' and I set up a new save handler with session_set_save_handler(), then afterwards I have to call session_write_close() at the end of every script, otherwise the session data doesn't get written out (to a database in my case) I tested it with PHP 4.0.6, and apache 1.3.20. PHP has to following extensions loaded: gd, mysql, ldap. ------------------------------------------------------------------------ Edit this bug report at http://bugs.php.net/?id=12915&edit=1-- Yasuo Ohgaki