ID: 36782 Updated by: [EMAIL PROTECTED] Reported By: webmaster at serverman dot de -Status: Feedback +Status: Bogus Bug Type: Session related Operating System: Suse 9.0 PHP Version: 4.4.2 New Comment:
Change open_basedir to include approriate directories. No bug here. Previous Comments: ------------------------------------------------------------------------ [2006-03-18 18:34:26] [EMAIL PROTECTED] I thought the question is quite clear.. ------------------------------------------------------------------------ [2006-03-18 18:27:01] webmaster at serverman dot de i don´t use session.save_handler files. i use session-save_handler user usr_webxx_xx is database ------------------------------------------------------------------------ [2006-03-18 18:12:41] [EMAIL PROTECTED] What is the value of open_basedir directive in phpinfo() and which file (usr_webxx_xx) are you trying to open? ------------------------------------------------------------------------ [2006-03-18 15:58:26] webmaster at serverman dot de Description: ------------ Hi, on Suse 9.0 using sassion.save_handler user and session.save_path usr_webxx_xx leads to an open_basedir restriction. Warning: Unknown(): open_basedir restriction in effect.File(usr_webxx_xx) is not within the allowed path(s): Seems as user in Php.ini is no longer recognized. Downgrading with the same compile string to 4.3.11, sessions are correct stored in datebase usr_webxx_xx. With 4.4.2 open_basedir with same vhost entries. Phpinfo shows correctly session.save_handlers files user mm Reproduce code: --------------- Try to store sessions in database with session.save_handler user session.save_path usr_webxx_xx <-- standing for your database. The used code works perfect with 4.3.11 Expected result: ---------------- Storing sessions to Database. Actual result: -------------- Open_basedir restrictions for files <-- although user is used ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=36782&edit=1
