When clients running the Firefox 1.0 access any page on the site, a NEW session id is saved in the session cookie (PHPSESSID by default).
We have trans sid turned off, which is default php behavior.
We require that cookies are used for session data.
We have custom session handlers defined. We use MySQL for session handling.
This is a problem because it makes logging into the site impossible.
After the login procedure is completed, the corresponding data is saved into the session table.
That data is tied to the current session id that the client holds in the cookie.
When the user navigates to another page in the site, a new session id is stored in the session cookie.
All of the data associated with the 'logged-in user' is now unaccessable for this client.
This leads me to believe that the session cookie is not being included in requests sent to the server. The server thinks this client is new and doesn't yet have a session, so it generates a new session id.
This problem does not happen for clients running IE6.
What are the steps to resolve this problem?
Are there "Gotcha's" with this type of setup that I am unaware of?
Thanks in advance,
Mrs. O'Toole - "Chinese girls do not come with green eyes.
We have trans sid turned off, which is default php behavior.
We require that cookies are used for session data.
We have custom session handlers defined. We use MySQL for session handling.
Code:
ini_set('session.use_only_cookies',1);
ini_set('session.save_handler', 'user');
After the login procedure is completed, the corresponding data is saved into the session table.
That data is tied to the current session id that the client holds in the cookie.
When the user navigates to another page in the site, a new session id is stored in the session cookie.
All of the data associated with the 'logged-in user' is now unaccessable for this client.
This leads me to believe that the session cookie is not being included in requests sent to the server. The server thinks this client is new and doesn't yet have a session, so it generates a new session id.
This problem does not happen for clients running IE6.
What are the steps to resolve this problem?
Are there "Gotcha's" with this type of setup that I am unaware of?
Thanks in advance,
Mrs. O'Toole - "Chinese girls do not come with green eyes.