Ask a Question related to PHP Bugs, Design and Development.
-
c dot kirschnick at gmx dot net #1
#40761 [NEW]: header() is wrongly handled, thus causing problems for browsers
From: c dot kirschnick at gmx dot net
Operating system: *
PHP version: 4.4.5
PHP Bug Type: CGI related
Bug description: header() is wrongly handled, thus causing problems for browsers
Description:
------------
This bug was sent in before, but marked wrong "bogus"/"won't fix". (See
Bug #38369).
PHP does not correctly handle calls such as header("Status: ..."). In
CGI mode it should process such a call as a changing the HTTP response
code (consistent with its handling of, e.g., header("Location: ...")).
However, at present there is no special handling of the Status: header.
That's why sending Status: and then Location: causes a duplicate header:
the Location: header is handled as a special case and causes
sapi_update_response_code(302) to be called, whereas the Status: header
is just added to the list of headers to be sent back to the web server
(see bug #33225 incorrectly marked "bogus", I think because the reviewer
doesn't understand CGI). Note that sending two different Status: headers
explicitly with header("Status: ...") doesn't give this error, because
the default operation is to *replace* the header, not add a new one.
Since PHP should conform to the CGI-norm, this bug should be fixed.
Although the IE does not fully stick to this norm, the FF does - which
ignores duplicated headers, resulting in different behaviour of both.
Reproduce code:
---------------
<?
header("HTTP/1.1 403 Forbidden");
?>
Expected result:
----------------
An error message created by the browser
Actual result:
--------------
IE: correct 403
FF: blank page (no output)
The headers:
HTTP/1.1 200 OK
HTTP/1.1 403 Forbidden
--
Edit bug report at [url]http://bugs.php.net/?id=40761&edit=1[/url]
--
Try a CVS snapshot (PHP 4.4): [url]http://bugs.php.net/fix.php?id=40761&r=trysnapshot44[/url]
Try a CVS snapshot (PHP 5.2): [url]http://bugs.php.net/fix.php?id=40761&r=trysnapshot52[/url]
Try a CVS snapshot (PHP 6.0): [url]http://bugs.php.net/fix.php?id=40761&r=trysnapshot60[/url]
Fixed in CVS: [url]http://bugs.php.net/fix.php?id=40761&r=fixedcvs[/url]
Fixed in release: [url]http://bugs.php.net/fix.php?id=40761&r=alreadyfixed[/url]
Need backtrace: [url]http://bugs.php.net/fix.php?id=40761&r=needtrace[/url]
Need Reproduce Script: [url]http://bugs.php.net/fix.php?id=40761&r=needscript[/url]
Try newer version: [url]http://bugs.php.net/fix.php?id=40761&r=oldversion[/url]
Not developer issue: [url]http://bugs.php.net/fix.php?id=40761&r=support[/url]
Expected behavior: [url]http://bugs.php.net/fix.php?id=40761&r=notwrong[/url]
Not enough info: [url]http://bugs.php.net/fix.php?id=40761&r=notenoughinfo[/url]
Submitted twice: [url]http://bugs.php.net/fix.php?id=40761&r=submittedtwice[/url]
register_globals: [url]http://bugs.php.net/fix.php?id=40761&r=globals[/url]
PHP 3 support discontinued: [url]http://bugs.php.net/fix.php?id=40761&r=php3[/url]
Daylight Savings: [url]http://bugs.php.net/fix.php?id=40761&r=dst[/url]
IIS Stability: [url]http://bugs.php.net/fix.php?id=40761&r=isapi[/url]
Install GNU Sed: [url]http://bugs.php.net/fix.php?id=40761&r=gnused[/url]
Floating point limitations: [url]http://bugs.php.net/fix.php?id=40761&r=float[/url]
No Zend Extensions: [url]http://bugs.php.net/fix.php?id=40761&r=nozend[/url]
MySQL Configuration Error: [url]http://bugs.php.net/fix.php?id=40761&r=mysqlcfg[/url]
c dot kirschnick at gmx dot net Guest
-
Flash causing browsers to crash, HELP!!!!
Each browser I have tried; IE 6, IE7, firefox 2.0, Netscape 8.1 all crash when i view flash sites. This happens on severl sites watching video or... -
#39314 [NEW]: imagecolorallocatealpha causing problems
From: slyc6 at aol dot com Operating system: Windows XP PHP version: 5.1.6 PHP Bug Type: *General Issues Bug description: ... -
Major Problems With Browsers
Ever since I installed Flash Player 8, Opera 8.51 has crashed on me every single time it tried viewing flash content. Firefox 1.5 tells me the... -
Problems with AOL/CS browsers
Hi All, I have run up against a strange error that seems affect only older version of AOL and CS browsers (AOL earlier than vs 8.0, and not sure... -
Weird Header Problem Causing Gap in Sliding
I'm having a problem with FMP6.0v4 on Mac OS 9.2.2 and Windows 2000. It's also happening on FMP5 and 5.5, but I'm going to be using 6. Depending on... -
tony2001@php.net #2
#40761 [Opn->Asn]: header() is wrongly handled, thus causing problems for browsers
ID: 40761
Updated by: [email]tony2001@php.net[/email]
Reported By: c dot kirschnick at gmx dot net
-Status: Open
+Status: Assigned
Bug Type: CGI related
Operating System: *
PHP Version: 4.4.5
-Assigned To:
+Assigned To: mike
Previous Comments:
------------------------------------------------------------------------
[2007-03-08 20:43:33] c dot kirschnick at gmx dot net
Description:
------------
This bug was sent in before, but marked wrong "bogus"/"won't fix". (See
Bug #38369).
PHP does not correctly handle calls such as header("Status: ..."). In
CGI mode it should process such a call as a changing the HTTP response
code (consistent with its handling of, e.g., header("Location: ...")).
However, at present there is no special handling of the Status:
header.
That's why sending Status: and then Location: causes a duplicate
header:
the Location: header is handled as a special case and causes
sapi_update_response_code(302) to be called, whereas the Status:
header
is just added to the list of headers to be sent back to the web server
(see bug #33225 incorrectly marked "bogus", I think because the
reviewer
doesn't understand CGI). Note that sending two different Status:
headers
explicitly with header("Status: ...") doesn't give this error, because
the default operation is to *replace* the header, not add a new one.
Since PHP should conform to the CGI-norm, this bug should be fixed.
Although the IE does not fully stick to this norm, the FF does - which
ignores duplicated headers, resulting in different behaviour of both.
Reproduce code:
---------------
<?
header("HTTP/1.1 403 Forbidden");
?>
Expected result:
----------------
An error message created by the browser
Actual result:
--------------
IE: correct 403
FF: blank page (no output)
The headers:
HTTP/1.1 200 OK
HTTP/1.1 403 Forbidden
------------------------------------------------------------------------
--
Edit this bug report at [url]http://bugs.php.net/?id=40761&edit=1[/url]
tony2001@php.net Guest
-
mike@php.net #3
#40761 [Asn->Fbk]: header() is wrongly handled, thus causing problems for browsers
ID: 40761
Updated by: [email]mike@php.net[/email]
Reported By: c dot kirschnick at gmx dot net
-Status: Assigned
+Status: Feedback
Bug Type: CGI related
Operating System: *
PHP Version: 4.4.5
Assigned To: mike
New Comment:
Please tell me your server software and your configure line.
Cannot reproduce with 4.4.3 and 4.4-CVS:
mike@honeybadger:~/build/php-4.4-cgi-http$ cgi <<<'<?php
header("HTTP/1.1 403 Forbidden");'
Status: 403
X-Powered-By: PHP/4.4.7-dev
Content-type: text/html
As you write
HTTP/1.1 200 OK
HTTP/1.1 403 Forbidden
as seen result, I think your server software exhibits this bug.
Previous Comments:
------------------------------------------------------------------------
[2007-03-08 20:43:33] c dot kirschnick at gmx dot net
Description:
------------
This bug was sent in before, but marked wrong "bogus"/"won't fix". (See
Bug #38369).
PHP does not correctly handle calls such as header("Status: ..."). In
CGI mode it should process such a call as a changing the HTTP response
code (consistent with its handling of, e.g., header("Location: ...")).
However, at present there is no special handling of the Status:
header.
That's why sending Status: and then Location: causes a duplicate
header:
the Location: header is handled as a special case and causes
sapi_update_response_code(302) to be called, whereas the Status:
header
is just added to the list of headers to be sent back to the web server
(see bug #33225 incorrectly marked "bogus", I think because the
reviewer
doesn't understand CGI). Note that sending two different Status:
headers
explicitly with header("Status: ...") doesn't give this error, because
the default operation is to *replace* the header, not add a new one.
Since PHP should conform to the CGI-norm, this bug should be fixed.
Although the IE does not fully stick to this norm, the FF does - which
ignores duplicated headers, resulting in different behaviour of both.
Reproduce code:
---------------
<?
header("HTTP/1.1 403 Forbidden");
?>
Expected result:
----------------
An error message created by the browser
Actual result:
--------------
IE: correct 403
FF: blank page (no output)
The headers:
HTTP/1.1 200 OK
HTTP/1.1 403 Forbidden
------------------------------------------------------------------------
--
Edit this bug report at [url]http://bugs.php.net/?id=40761&edit=1[/url]
mike@php.net Guest
-
c dot kirschnick at gmx dot net #4
#40761 [Fbk->Csd]: header() is wrongly handled, thus causing problems for browsers
ID: 40761
User updated by: c dot kirschnick at gmx dot net
Reported By: c dot kirschnick at gmx dot net
-Status: Feedback
+Status: Closed
Bug Type: CGI related
Operating System: *
PHP Version: 4.4.5
Assigned To: mike
New Comment:
Hum, tried it again and again - came to the conclusion that it was a
browser issue.
Sorry, and keep up the good work.
Previous Comments:
------------------------------------------------------------------------
[2007-03-09 11:14:34] [email]mike@php.net[/email]
Please tell me your server software and your configure line.
Cannot reproduce with 4.4.3 and 4.4-CVS:
mike@honeybadger:~/build/php-4.4-cgi-http$ cgi <<<'<?php
header("HTTP/1.1 403 Forbidden");'
Status: 403
X-Powered-By: PHP/4.4.7-dev
Content-type: text/html
As you write
HTTP/1.1 200 OK
HTTP/1.1 403 Forbidden
as seen result, I think your server software exhibits this bug.
------------------------------------------------------------------------
[2007-03-08 20:43:33] c dot kirschnick at gmx dot net
Description:
------------
This bug was sent in before, but marked wrong "bogus"/"won't fix". (See
Bug #38369).
PHP does not correctly handle calls such as header("Status: ..."). In
CGI mode it should process such a call as a changing the HTTP response
code (consistent with its handling of, e.g., header("Location: ...")).
However, at present there is no special handling of the Status:
header.
That's why sending Status: and then Location: causes a duplicate
header:
the Location: header is handled as a special case and causes
sapi_update_response_code(302) to be called, whereas the Status:
header
is just added to the list of headers to be sent back to the web server
(see bug #33225 incorrectly marked "bogus", I think because the
reviewer
doesn't understand CGI). Note that sending two different Status:
headers
explicitly with header("Status: ...") doesn't give this error, because
the default operation is to *replace* the header, not add a new one.
Since PHP should conform to the CGI-norm, this bug should be fixed.
Although the IE does not fully stick to this norm, the FF does - which
ignores duplicated headers, resulting in different behaviour of both.
Reproduce code:
---------------
<?
header("HTTP/1.1 403 Forbidden");
?>
Expected result:
----------------
An error message created by the browser
Actual result:
--------------
IE: correct 403
FF: blank page (no output)
The headers:
HTTP/1.1 200 OK
HTTP/1.1 403 Forbidden
------------------------------------------------------------------------
--
Edit this bug report at [url]http://bugs.php.net/?id=40761&edit=1[/url]
c dot kirschnick at gmx dot net Guest
-
tony2001@php.net #5
#40761 [Csd->Bgs]: header() is wrongly handled, thus causing problems for browsers
ID: 40761
Updated by: [email]tony2001@php.net[/email]
Reported By: c dot kirschnick at gmx dot net
-Status: Closed
+Status: Bogus
Bug Type: CGI related
Operating System: *
PHP Version: 4.4.5
Assigned To: mike
Previous Comments:
------------------------------------------------------------------------
[2007-03-09 14:24:56] c dot kirschnick at gmx dot net
Hum, tried it again and again - came to the conclusion that it was a
browser issue.
Sorry, and keep up the good work.
------------------------------------------------------------------------
[2007-03-09 11:14:34] [email]mike@php.net[/email]
Please tell me your server software and your configure line.
Cannot reproduce with 4.4.3 and 4.4-CVS:
mike@honeybadger:~/build/php-4.4-cgi-http$ cgi <<<'<?php
header("HTTP/1.1 403 Forbidden");'
Status: 403
X-Powered-By: PHP/4.4.7-dev
Content-type: text/html
As you write
HTTP/1.1 200 OK
HTTP/1.1 403 Forbidden
as seen result, I think your server software exhibits this bug.
------------------------------------------------------------------------
[2007-03-08 20:43:33] c dot kirschnick at gmx dot net
Description:
------------
This bug was sent in before, but marked wrong "bogus"/"won't fix". (See
Bug #38369).
PHP does not correctly handle calls such as header("Status: ..."). In
CGI mode it should process such a call as a changing the HTTP response
code (consistent with its handling of, e.g., header("Location: ...")).
However, at present there is no special handling of the Status:
header.
That's why sending Status: and then Location: causes a duplicate
header:
the Location: header is handled as a special case and causes
sapi_update_response_code(302) to be called, whereas the Status:
header
is just added to the list of headers to be sent back to the web server
(see bug #33225 incorrectly marked "bogus", I think because the
reviewer
doesn't understand CGI). Note that sending two different Status:
headers
explicitly with header("Status: ...") doesn't give this error, because
the default operation is to *replace* the header, not add a new one.
Since PHP should conform to the CGI-norm, this bug should be fixed.
Although the IE does not fully stick to this norm, the FF does - which
ignores duplicated headers, resulting in different behaviour of both.
Reproduce code:
---------------
<?
header("HTTP/1.1 403 Forbidden");
?>
Expected result:
----------------
An error message created by the browser
Actual result:
--------------
IE: correct 403
FF: blank page (no output)
The headers:
HTTP/1.1 200 OK
HTTP/1.1 403 Forbidden
------------------------------------------------------------------------
--
Edit this bug report at [url]http://bugs.php.net/?id=40761&edit=1[/url]
tony2001@php.net Guest



Reply With Quote

