php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #36400 Custom 5xx error does not return correct HTTP response error code
Submitted: 2006-02-15 10:12 UTC Modified: 2006-02-15 12:11 UTC
From: paolo at casarini dot org Assigned:
Status: Closed Package: Apache related
PHP Version: 5.1.2 OS: Linux version 2.4.27-2-386
Private report: No CVE-ID: None
View Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
If you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: paolo at casarini dot org
New email:
PHP Version: OS:

 

 [2006-02-15 10:12 UTC] paolo at casarini dot org 
Description:
------------
When running PHP as an Apache module (Apache/1.3.34 (Debian) PHP/5.1.2-1.dotdeb.2 mod_ssl/2.8.25 OpenSSL/0.9.8), the
response error code for a custom error is not correctly returned.

Reproduce code:
---------------
<?php
header("HTTP/1.1 559 CustomError");
header("Status: 559 CustomError");
echo "<html>\n";
echo "<body>\n";
echo "Error on page!!!\n";
echo "</body>\n";
echo "</html>\n";
?>

Expected result:
----------------
I would expect to see an HTTP response code of 559 with a response message of "CustomError".

Actual result:
--------------
The response code returned is 500.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2006-02-15 12:11 UTC] tony2001@php.net 
This bug has been fixed in CVS.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
 
Thank you for the report, and for helping us make PHP better.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Tue Dec 03 17:01:29 2024 UTC