Bug #15909 Updated: Session data not updated on page jump (header() may be the cause)

From: Date: Wed, 27 Mar 2002 02:44:56 +0000
Subject: Bug #15909 Updated: Session data not updated on page jump (header() may be the cause)
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-3446@lists.php.net to get a copy of this message
 ID:               15909
 Updated by:       yohgaki@php.net
-Summary:          Session data not updated on page jump
 Reported By:      phpbug@ehrlichorg.com
-Status:           Open
+Status:           Feedback
 Bug Type:         Session related
 Operating System: Linux Gnu  2.2.12
 PHP Version:      4.1.2
 New Comment:

Could you limit size of max text size returned from MySQL?
Does it help?


Previous Comments:
------------------------------------------------------------------------

[2002-03-26 11:55:03] phpbug@ehrlichorg.com

Yes, we are using MySQL 3.23.38 in the application. However, the
session.save_handler is files. 

We were using the same version of MySQL with PHP 4.0.2.

------------------------------------------------------------------------

[2002-03-26 00:40:21] yohgaki@php.net

Do you use MySQL?


------------------------------------------------------------------------

[2002-03-25 21:15:04] phpbug@ehrlichorg.com

PHP Does not appear to be seg faulting; nothing in the logs indicates
that type of error.

------------------------------------------------------------------------

[2002-03-25 05:09:49] yohgaki@php.net

Hmm. It sounds like PHP is segfaulting. (Or bailing out without proper
shutdown)
If you are having segfualts, could you build PHP with --enable-debug
and send the backtrace?




------------------------------------------------------------------------

[2002-03-25 03:18:27] irenem@ms2.hinet.net

It looks like the PHP 4.1.2 forgot to call session_write_close() by
default. I added this call at the end of my program, and solved this
session problem.

------------------------------------------------------------------------

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/15909

-- 
Edit this bug report at http://bugs.php.net/?id=15909&edit=1



Thread (22 messages)

« previous php.bugs (#3446) next »