Bug #74094 [Opn]: Too strict checks when using CLI SAPI

From: Date: Tue, 21 Feb 2017 10:44:19 +0000
Subject: Bug #74094 [Opn]: Too strict checks when using CLI SAPI
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-207485@lists.php.net to get a copy of this message 
Edit report at https://bugs.php.net/bug.php?id=74094&edit=1

 ID:                 74094
 Updated by:         yunosh@php.net
 Reported by:        yunosh@php.net
 Summary:            Too strict checks when using CLI SAPI
 Status:             Open
 Type:               Bug
 Package:            Session related
 PHP Version:        master-Git-2017-02-13 (Git)
 Block user comment: N
 Private report:     N

 New Comment:

I wonder if SG(request_info).no_headers should be set to 1 in the CLI SAPI.


Previous Comments:
------------------------------------------------------------------------
[2017-02-13 18:04:23] yunosh@php.net

This can be seen in real life here: https://travis-ci.org/horde/horde/jobs/201207489#L1860

------------------------------------------------------------------------
[2017-02-13 18:01:26] yunosh@php.net

Description:
------------
When using the CLI SAPI, it doesn't make sense to implement the same strict HTTP header checks
like in webserver SAPIs IMO. There are no headers sent in this case, so the error messages are at
least misleading.
As a consequence, it makes unit testing of session related code impossible, because unit testing
frameworks usually produce output before even running a single test.



------------------------------------------------------------------------



--
Edit this bug report at https://bugs.php.net/bug.php?id=74094&edit=1

Thread (4 messages)

« previous php.bugs (#207485) next »