Bug #76724 [Ver]: Unable to start session when using PHP CGI

Edit report at https://bugs.php.net/bug.php?id=76724&edit=1 ID: 76724 Updated by: requinix@php.net Reported by: geral at braldesign dot com Summary: Unable to start session when using PHP CGI Status: Verified Type: Bug Package: Session related Operating System: CLOUDLINUX 6.10 standard PHP Version: 7.2.8 Block user comment: N Private report: N New Comment: php-cli should be used for cronjobs, yes, but this bug report is about php-cgi. They are not the same. Either you are using php-cli and this bug is irrelevant, or you are using php-cgi and you should not be. And you know sessions don't really work from the command line, right? You would have to force a particular session ID, new or existing, for sessions to work across multiple runs. Previous Comments: ------------------------------------------------------------------------ [2018-08-09 09:28:27] spam2 at rhsoft dot net a proper software runtime skips session_start() when not running within a webserver environment, these are a few lines of PHP code and be it only to prevent spit session files to disk for no gain ------------------------------------------------------------------------ [2018-08-09 09:24:14] geral at braldesign dot com I'm using the php-cli only because it is the default used by cron jobs and i'm using session on it just because the script uses session to store data for the execution. If this behavior is intended I can only work around it. Thanks for the explanation. ------------------------------------------------------------------------ [2018-08-09 09:19:05] requinix@php.net Well, without knowing what you're doing or why, I would suggest using the regular PHP binary instead of php-cgi. ------------------------------------------------------------------------ [2018-08-09 09:17:49] geral at braldesign dot com Then, there is no way to use a session with a quiet script? thanks. ------------------------------------------------------------------------ [2018-08-09 09:14:31] requinix@php.net -q deliberately makes the scripting engine think that headers have been sent, but it's been that way for so long that I can't say exactly why it does so. I can only assume there is/was a good reason. ------------------------------------------------------------------------ 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 https://bugs.php.net/bug.php?id=76724 -- Edit this bug report at https://bugs.php.net/bug.php?id=76724&edit=1