i have a strange problem wherein if a user has cookies turned off, he cannot log into phpsecurityadmin. i have customized the software to work with several different sites, so i have changed the names of some tables to suit their needs. one burning question i have is related to the save_handler that is set in the sessions.php file. why is it set to "user"? what is the significance of that name? i am thinking that somehow, by using different table names i might have missed something related to this. it seems like the sessionID is being stored in the database and in the client side cookie, and login is unsuccessful if the client has cookies turned off.
this is on a redhat 8 server, apache 1.2.30, php4.3.8 and the phpsecurityadmin software is version 3.0b.
thanks in advance.
yours,
steve
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When I started developing this class, I think the latest PHP version was something like 4.0.6. At that time, I think that the session.save_handler needed to be set to user in order for the custom session handling classes to work.
Since then, PHP's implementation of the save_handler ini setting and the use of set_session_save_handler may have changed so that one does not depend on the other. (I haven't looked into this).
In either case, the ini setting does not have anything to do with the database table names. Its a PHP-internal type of thing.
You may want to check your session.use_cookies and session_use_only_cookies settings in your php.ini file as well to see if those are cuasing you problems.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
greetings,
i have a strange problem wherein if a user has cookies turned off, he cannot log into phpsecurityadmin. i have customized the software to work with several different sites, so i have changed the names of some tables to suit their needs. one burning question i have is related to the save_handler that is set in the sessions.php file. why is it set to "user"? what is the significance of that name? i am thinking that somehow, by using different table names i might have missed something related to this. it seems like the sessionID is being stored in the database and in the client side cookie, and login is unsuccessful if the client has cookies turned off.
this is on a redhat 8 server, apache 1.2.30, php4.3.8 and the phpsecurityadmin software is version 3.0b.
thanks in advance.
yours,
steve
When I started developing this class, I think the latest PHP version was something like 4.0.6. At that time, I think that the session.save_handler needed to be set to user in order for the custom session handling classes to work.
Since then, PHP's implementation of the save_handler ini setting and the use of set_session_save_handler may have changed so that one does not depend on the other. (I haven't looked into this).
In either case, the ini setting does not have anything to do with the database table names. Its a PHP-internal type of thing.
You may want to check your session.use_cookies and session_use_only_cookies settings in your php.ini file as well to see if those are cuasing you problems.