ID:               34542
 Comment by:       mail at lenzw dot de
 Reported By:      marcus dot uy at virtualthinking dot com
 Status:           Feedback
 Bug Type:         Session related
 Operating System: WinXP Pro
 PHP Version:      5.1.0RC4
 New Comment:

see Bug #33811 for a reproduction code.


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

[2005-11-03 22:10:18] [EMAIL PROTECTED]

Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves. 

A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external 
resources such as databases, etc.

If possible, make the script source available online and provide
an URL to it here. Try to avoid embedding huge scripts into the report.



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

[2005-11-03 16:47:25] marcus dot uy at virtualthinking dot com

Hi, I think somebody else has a related problem with a workable test
case.

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

[2005-11-03 09:36:44] marcus at synchromedia dot co dot uk

I think I'm seeing this same bug in 5.1.0RC4. I'm not 
getting exactly the same symptom, but it's close. I'm 
finding that session files are created no problem, but when 
I change values in $_SESSION, the changes are not saved, 
even if I use session_write_close(). I've set up a small 
test case that is storing and changing exactly what I'm 
doing in my project and it doesn't happen, so I don't think 
it's a problem with the contents of the session. I also 
wrote a test that stuffed 5000 strings into $_SESSION and 
that worked ok too.
Like the original bug report, it all works fine if I leave 
register_long_arrays turned on, even though I'm not using 
them anywhere in my code, or in libraries that I'm using.
What I would like to do is do a trace with xdebug and look 
at everything that involves sessions, but I can't at present 
because xdebug-cvs won't run under 5.1.0RC4.

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

[2005-09-19 13:47:45] [EMAIL PROTECTED]

Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves. 

A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external 
resources such as databases, etc.

If possible, make the script source available online and provide
an URL to it here. Try to avoid embedding huge scripts into the report.



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

[2005-09-19 12:38:07] marcus dot uy at virtualthinking dot com

Hi just tried it with the CVS versions to popinted me to.  No dice.

Same problem.  After the session is created as a zero-length file and
updating $_SESSION in the script does nothing to change this.

The values are accessible during the first run, and when re-read on
subsequent runs, understandably return an empty $_SESSION array.

FYI, my application is split into a public http system and a private
https system.  The session sticks in the http session, but as noted
earlier, the number of session values used is significantly less than
after a user has logged in the https session.

I allow the script to generate a new SID for the https session as I do
not need to pass over the values, and it is here that the values do not
stick.

Both the http and https sites share an *indentical* code base so it's
not a program error.

Erm, to be honest the code I posted is cut down to allow for it to be a
reasonable length.  It incorporates the essentials of the problem, but
perhaps not the full environment.

It still needs the register_long_arrays to be "on" before it will work.

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

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