ID:               34542
 Updated by:       [EMAIL PROTECTED]
 Reported By:      marcus dot uy at virtualthinking dot com
-Status:           Open
+Status:           Feedback
 Bug Type:         Session related
 Operating System: WinXP Pro
 PHP Version:      5.1.0RC4, 5.2.0
 New Comment:

>Like on Windows, "register_long_arrays=On" causes the
> described problem with the session too.
No, it doesn't.
With register_long_arrays=On I get the same result, as with Off. It
works perfectly fine.

I guess you have some kind of broken browser and/or some combination of
Apache modules or PHP/Zend extensions, which cause it. By the way, you
didn't answer my question on zend_extensions.


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

[2006-12-05 15:12:33] marcus dot uy at virtualthinking dot com

Just a quick update.  A correction on the Linux settings.  Like on
Windows, "register_long_arrays=On" causes the described problem with
the session too.

My bad.  Did not notice that the option was commented out.

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

[2006-11-29 12:15:40] marcus dot uy at virtualthinking dot com

mod_security removed.  Behaviour of PHP is still the same as my
previous post.

I have tested the same php.ini file on a separate linux server (with
path names adjusted for linux) that I own and it works with
register_long_arrays=off in the expected manner as documented.

The same settings on windows fail to work as noted earlier.

I cannot verify this, but is there some internal reference or
dependency in the session subsystem that uses the old long array
vars/buffer as the input source for the data that is written to the
session file?

Hence:

$_SESSION => can show up during the run
...but...
$HTTP_SESSION_VAR => written to disk, and thus empty

Any chance?  Was discussing fault scenarios with a friend and this came
up as a plausible case that would result in this kind of oddity (a
difference in how the windows and linux compilers work might account
for the difference in behaviour on different platforms???).

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

[2006-11-29 10:08:15] [EMAIL PROTECTED]

First of all, please remove/disable mod_security.

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

[2006-11-29 01:19:02] marcus dot uy at virtualthinking dot com

Dev/Tester.  Please tell us what your setup is.  Mine is as follows:

XPPro SP2, Apache 2.2.3, mod_security 2.0.4, PHP5.2.0

Settings as per recommended for performance.

Sessions configured to use URL, NOT cookies.

Sessions are being stored in C:\temp\sessiondata

When register_long_arrays is set to "off", Session data is created in
the script on first execute (print_r($_SESSION), dumps correctly), but
not saved to session file (e.g. sess_34r234r234r234r234r234, is
zero-length)

When register_long_arrays is set to "on", Session data is created in
the script on first execute (print_r($_SESSION), dumps correctly), and
is saved to session file (e.g. sess_34r234r234r234r234r234, is
non-zero-length)

The code does not use *any* HTTP_*_VARS... anywhere.  Only $_ENV,
$_GET, $_POST, and $_SESSION.  $_COOKIES is *not* used anywhere.

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

[2006-11-28 22:48:18] [EMAIL PROTECTED]

Cannot reproduce, doesn't matter what is the value of
register_long_arrays. Please make sure you don't have any firewalls or
zend_extension's which might affect it.

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

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

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

Reply via email to