$_SESSION data loss

gaucho

Hello,
I have a problem with holding data in the $SESSION variable.
Session setup/initialization works fine, Some of the data I pass to the $SESSION variable also persists during the whole session with no problem.
I'm also using the $SESSION variable to store some app data as long as it is needed, this is to replace the hidden fields in forms.
Well, this works fine as long as I only store a small number of records in the $SESSION variable. If the number of records passes around 15 to 20 records the variable is empty on the next page, and this is the problem.
Well, to become a little more specific, I specified an array called "data". Entering a page section $SESSION['data'] is filled with database records. This works fine, dumping the $SESSION variable shows me that filling the array works. As long as I only store just a few records, data is passed to the next page or reloaded page with no problem. But like I said, with more than 15 to 20 records, this doesn't work any more. The rest of the arrays im my $_SESSION variable still exist.

Does anybody have an idea where the problem could come from?
As far as I know there should not be any problem even storing millions of records in an array.

Many thanks in advance

Gaucho

olaf

Hallo,

i'm sure that its not a problem of the array. But maybe there is a limit for the sessions. Do you have this problem local and remote?

gaucho

Hi Olaf,
thanks for the reply.
Yes connection type don't matter.

Greetz

gaucho

cl_stef

I had the same problem when I was using cookies as session handler, all my session records disappeared from time to time while the user was browsing the webpages.
The use of server-based files as session handler solved the problem, it seems to be better in all cases, talking about both reliability and security.

gaucho

Hi,
well, I'm using server-side sessions too. The only thing needed is a session cookie that holds the ID. Furthermore I'm not only using files but using a database table to store the session data. I mean, I wouldn't wonder if all of the session data would get lost, but it is only just parts, and only if the data-part grows behind a certain size, and this is just a really small size.

Any idea?

Many thanks

gaucho

I forgot,
I was just thinking about a way to solve this, at least temporarilly, and I would be interested in your opinion.
Well, a while ago I had to write a little script to save configuration settings, maybe not the regular way, but in a php-file I could include on runtime, holding a configuration array like this:

<?php

$config[0]['setting1'] = .....;
etc.
?>

This way I could include the file when needed and had direct access to the array. This works fine and seems to be even fast.

Maybe this would be a way to solve the problem. The variables would be visible to the application but not to the user, this way I could get away from hidden fields. I'm thinking about creating the file when necessary at runtime, giving it the name of the session ID. Only problem would be the garbage collection.

What do you think about this. This is only just in case nobody finds a solution to the $_SESSION-variable problem.

Best regards

gaucho

cl_stef

So you store information in your a mysql table, do they appear clearly, or are they encrypted?
You may try to create a blank web page which adds one value in the session each time it is loaded, call this page many times and have a look in the database after each step.

Or use only server side files as session handler if possible, it would solve all your problems.

gaucho

They are encrypted.
And I don't think that the storage could be the problem, because I'm using ADODB ADODB for session management, which is well tested as far as I know.

Cheers

gaucho