Bug #55850 [Opn->Ver]: header() / setcookie() / session_start() give bogus warning
| From: | cmb@php.net | Date: | Wed, 24 Jun 2015 18:44:19 +0000 |
| Subject: | Bug #55850 [Opn->Ver]: header() / setcookie() / session_start() give bogus warning | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-193855@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=55850&edit=1
ID: 55850
Updated by: cmb@php.net
Reported by: tklingeberg at lastflood dot net
Summary: header() / setcookie() / session_start() give bogus
warning
-Status: Open
+Status: Verified
Type: Bug
Package: CGI/CLI related
-Operating System: Linux
+Operating System: *
-PHP Version: 5.3.8
+PHP Version: 5.6.10
Block user comment: N
Private report: N
New Comment:
Confirmed: <http://3v4l.org/CYsUm>.
Previous Comments:
------------------------------------------------------------------------
[2011-10-04 23:38:05] tklingeberg at lastflood dot net
Description:
------------
SAPIs that do not support HTTP header(s), give warnings that output has been already sent like
"Warning: Cannot modify header information - headers already sent by..."
even those APIs do *not* support headers.
There is no use to warn about something that can never happen; There is nothing to modify; There are
no headers that already have been sent.
It might make more sense to warn that this function is useless w/o HTTP response headers being
available.
Compare with headers_sent(), it does differ between SAPIs.
Would be nice to have this a bit more streamlined.
Additionally header() could return FALSE if it failed like setcookie().
Test script:
---------------
In CLI:
<?php
echo "output";
session_start();
setcookie("TestCookie", 'value');
header('X-TestHeader: value');
?>
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=55850&edit=1