ID: 15909
Updated by: [EMAIL PROTECTED]
-Summary: Session data not updated on page jump (header() may be
the cause)
-Reported By: [EMAIL PROTECTED]
+Reported By: [EMAIL PROTECTED]
-Status: Open
+Status: Feedback
Bug Type: Session related
-Operating System: Linux Gnu 2.2.12
+Operating System: Linux (Debian)
-PHP Version: 4.1.2
+PHP Version: 4.1.1
New Comment:
There is bug report for MySQL.
After serval database operation, calling heade() crashes PHP for some
reason according to the bug report.
Anyway, I don't use MySQL and I don't have this problem.
We need backtrace or need where/how PHP is bailing out.
Build with --enable-debug and check what is going to with debugger.
Previous Comments:
------------------------------------------------------------------------
[2002-03-27 12:02:40] [EMAIL PROTECTED]
Sorry, I don't see where I would limit size of max text size returned
from MySQL or what you are looking for. Please clarify.
The applications that are not working are not using large text fields.
Most are defined as TINYTEXT and TEXT. There are a couole of columns
defined as MEDIUMTEXT (due to misunderstanding of field types) but the
contents are less than 4000 bytes.
------------------------------------------------------------------------
[2002-03-26 21:44:55] [EMAIL PROTECTED]
Could you limit size of max text size returned from MySQL?
Does it help?
------------------------------------------------------------------------
[2002-03-26 11:55:03] [EMAIL PROTECTED]
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] [EMAIL PROTECTED]
Do you use MySQL?
------------------------------------------------------------------------
[2002-03-25 21:15:04] [EMAIL PROTECTED]
PHP Does not appear to be seg faulting; nothing in the logs indicates
that type of error.
------------------------------------------------------------------------
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
