Visite Webhosting Latino, el site sobre alojamiento web.
#25044 : header("Location:") changing HTTP status - Mombu the Php Forum
Mombu the Php Forum sponsored links

Go Back   Mombu the Php Forum > Php > #25044 : header("Location:") changing HTTP status
User Name
REGISTER NOW! Mark Forums Read

sponsored links

1 12th May 06:14
External User
Posts: 1
Default #25044 : header("Location:") changing HTTP status

ID: 25044
Updated by:
Reported By: seairth at cox dot net
-Status: Open
+Status: Closed
Bug Type: HTTP related
-Operating System: N/A
+Operating System: *
-PHP Version: Irrelevant
+PHP Version: 4.3.3-RC3
Assigned To: helly
New Comment:

This bug has been fixed in CVS.

In case this was a PHP problem, snapshots of the sources are packaged
every three hours; this change will be in the next snapshot. You can
grab the snapshot at

In case this was a do***entation problem, the fix will show up soon at

In case this was a website problem, the change will show
up on the site and on the mirror sites in short time.

Thank you for the report, and for helping us make PHP better.

Previous Comments:

[2003-08-11 12:10:32] seairth at cox dot net

When setting the "Location" HTTP header using the header() function,
PHP automatically changes the HTTP response status to "302 Found".
However, there are several other legitimate status codes that use the
Location header. These codes include 201, 301, 303, 305, and 307
(according to the HTTP 1.1 spec). When one of these status codes is
already set, setting the Location header should not change it.

Note: there is a workaround. (re)Set the status after setting the
Location header. However, this is not a reasonable solution. For
those codes listed above, it should not matter whether the status is
set before or after the Location header.

It may even be appropriate to not change the status for any value other
than 200 (the default). As a result, if a user ********ly sets the
status to something other than 200, then setting the Location header
should not change that value again (even if the combination of the
status and header do not make sense). The reasoning here is that HTTP
status codes are extensible, meaning that new specifications can add
new status codes that may use the Location header. If only testing for
the above list, new codes would be overlooked and therefore
automatically changed.

Reproduce code:
header('HTTP/1.1 201 Created');

Expected result:
HTTP Response:

HTTP/1.1 201 Created

Actual result:
HTTP Response:

HTTP/1.0 302 Found


Edit this bug report at
  Reply With Quote

  sponsored links


Thread Tools
Display Modes

Copyright 2006 - Dies Mies Jeschet Boenedoesef Douvema Enitemaus -