|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #55850 header() / setcookie() / session_start() give bogus warning
Submitted: 2011-10-04 23:38 UTC Modified: 2015-06-24 18:44 UTC
Avg. Score:2.1 ± 1.3
Reproduced:4 of 5 (80.0%)
Same Version:0 (0.0%)
Same OS:3 (75.0%)
From: tklingeberg at lastflood dot net Assigned:
Status: Verified Package: CGI/CLI related
PHP Version: 5.6.10 OS: *
Private report: No CVE-ID: None
Have you experienced this issue?
Rate the importance of this bug to you:

 [2011-10-04 23:38 UTC] tklingeberg at lastflood dot net
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:

echo "output";
setcookie("TestCookie", 'value');
header('X-TestHeader: value');


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2015-06-24 18:44 UTC]
-Status: Open +Status: Verified -Operating System: Linux +Operating System: * -PHP Version: 5.3.8 +PHP Version: 5.6.10
 [2015-06-24 18:44 UTC]
Confirmed: <>.
PHP Copyright © 2001-2023 The PHP Group
All rights reserved.
Last updated: Tue Mar 21 04:03:39 2023 UTC