|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #47605 CGI SAPI can not send HTTP 200 header
Submitted: 2009-03-09 14:45 UTC Modified: 2009-05-06 08:15 UTC
Avg. Score:4.5 ± 0.5
Reproduced:2 of 2 (100.0%)
Same Version:2 (100.0%)
Same OS:1 (50.0%)
From: c dot c dot dean at durham dot ac dot uk Assigned:
Status: Open Package: CGI/CLI related
PHP Version: 5.*, 6CVS (2009-04-25) OS: *
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Bug Type:
From: c dot c dot dean at durham dot ac dot uk
New email:
PHP Version: OS:


 [2009-03-09 14:45 UTC] c dot c dot dean at durham dot ac dot uk
If you invoke header("HTTP/1.0 200 OK"); from PHP in CGI mode, the header is never output, because it's suppressed at line 379 in sapi/cgi/cgi_main.c.  If you use any value other than 200, it is output correctly.

This means for instance, that if you use PHP in CGI mode as an Apache errordocument handler, you cannot send back a non-error 200 OK to the user.

The following trivial change fixes this, but you might prefer a more elegant solution.

--- php-5.2.9/sapi/cgi/cgi_main.c.orig   2009-01-19 18:17:59.000000000 +0000
+++ php-5.2.9/sapi/cgi/cgi_main.c       2009-03-09 14:04:11.000000000 +0000
@@ -376,7 +376,7 @@
                return  SAPI_HEADER_SENT_SUCCESSFULLY;

-       if (CGIG(nph) || SG(sapi_headers).http_response_code != 200)
+       if (CGIG(nph) || SG(sapi_headers).http_response_code != 666)
                int len;
                zend_bool has_status = 0;
@@ -914,7 +914,7 @@
        SG(request_info).request_uri = NULL;
        SG(request_info).content_type = NULL;
        SG(request_info).content_length = 0;
-       SG(sapi_headers).http_response_code = 200;
+       SG(sapi_headers).http_response_code = 666;

        /* script_path_translated being set is a good indication that
           we are running in a cgi environment, since it is always

Reproduce code:
Use this as the Apache errordocument handler:

  header("HTTP/1.0 200 OK");
  echo "This is OK";

Expected result:
HTTP/1.0 200 OK in the header and "This is OK" in the body

Actual result:
HTTP/1.0 404 Not Found


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2009-04-25 16:00 UTC]
What have you set cgi.nph to? Try disabling it first.

(See also bug #27026 as this fix changed the behaviour)

 [2009-04-27 09:52 UTC] c dot c dot dean at durham dot ac dot uk
With cgi.nph = 0, no status header is output unless you invoke header(), and then only if your status code isn't 200.

With cgi.nph = 1, a status header is always output, defaulting to 200 if header() is not invoked.

What I'd like, and other people have requested, is a situation where a    status header is output if and only if you invoke header(), and without any special case for 200.

In my view, this should be the default behaviour, but if you think that breaks backward compatibility, could you instead implement it by allowing cgi.nph = 2 to trigger it?


 [2009-05-05 18:45 UTC]
Does it works with a "Status: 200 OK" header instead of "HTTP/1.0 200 OK" ?
 [2009-05-06 08:15 UTC] c dot c dot dean at durham dot ac dot uk
Yes, if you use "Status: 200 OK", it does work, so I guess
that's a workaround, but it's not very intuitive for this
to behave differently to "HTTP/1.0 200 OK".


PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Sun Apr 18 21:01:24 2021 UTC