#39984 [Sus]: Response header sent as 302 despite being set to 301
From: marc dot bau at gmx dot net Date: Fri, 23 Feb 2007 13:28:44 +0000 Subject: #39984 [Sus]: Response header sent as 302 despite being set to 301 References: 1 Groups: php.bugs Request: Send a blank email to php-bugs+get-109400@lists.php.net to get a copy of this message
ID: 39984
User updated by: marc dot bau at gmx dot net
Reported By: marc dot bau at gmx dot net
Status: Suspended
Bug Type: IIS related
Operating System: WinXP
PHP Version: 5.2.1
Assigned To: edink
New Comment:
i wonder why there shouldn't be a way to handle this.
As one example ActiveState (www.activestate.com) Perl have a CGI
version and this works well, too. You should spend some time on the
Perl Code, maybe there is a small trick inside.
Previous Comments:
------------------------------------------------------------------------
[2007-02-19 23:23:06] edink@php.net
Seems that there is no way a CGI script can convince IIS to output
something else than 302 response if you have location header.
Same IIS using Microsofts latest FCGI isapi has no problems with PHP
outputing correct status code.
I recommend that you switch to that instead of using raw cgi, the
perfomance icrease is dramatic as well.
http://www.iis.net/default.aspx?tabid=1000051
------------------------------------------------------------------------
[2007-02-18 12:05:02] marc dot bau at gmx dot net
Additional to this a header('HTTP/1.0 404 Not Found') produces a "404
OK".
------------------------------------------------------------------------
[2007-01-11 10:02:47] tony2001@php.net
Edin, could you plz verify if this problem is still valid?
------------------------------------------------------------------------
[2007-01-04 22:14:28] marc dot bau at gmx dot net
open
------------------------------------------------------------------------
[2007-01-01 17:03:04] marc dot bau at gmx dot net
If Perl, ColdFusion and ASP Pages are correct and PHP not, what do you
think is wrong?
I think PHP! Maybe there is something wrong in the way how the status
is set or how the status is transfered to IIS... i don't know if there
is something special in IIS, but it looks like a PHP Bug, while all
other script languages are correct.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/39984
--
Edit this bug report at http://bugs.php.net/?id=39984&edit=1
Thread (29 messages)
- #39984 [Opn->Fbk]: Response header sent as 302 despite being set to 301
- #39984 [Fbk->Opn]: Response header sent as 302 despite being set to 301
- #39984 [Opn->Fbk]: Response header sent as 302 despite being set to 301
- #39984 [Fbk->Opn]: Response header sent as 302 despite being set to 301
- #39984 [Opn]: Response header sent as 302 despite being set to 301
- #39984 [Opn->Fbk]: Response header sent as 302 despite being set to 301
- #39984 [Fbk->Opn]: Response header sent as 302 despite being set to 301
- #39984 [Opn]: Response header sent as 302 despite being set to 301
- #39984 [Opn->Fbk]: Response header sent as 302 despite being set to 301
- #39984 [Fbk->Opn]: Response header sent as 302 despite being set to 301
- #39984 [Opn->Csd]: Response header sent as 302 despite being set to 301
- #39984 [Csd]: Response header sent as 302 despite being set to 301
- #39984 [Csd->Opn]: Response header sent as 302 despite being set to 301
- #39984 [Opn]: Response header sent as 302 despite being set to 301
- #39984 [Opn->Fbk]: Response header sent as 302 despite being set to 301
- #39984 [Fbk->Opn]: Response header sent as 302 despite being set to 301
- #39984 [Opn->Csd]: Response header sent as 302 despite being set to 301
- #39984 [Csd]: Response header sent as 302 despite being set to 301
- #39984 [Csd]: Response header sent as 302 despite being set to 301
- #39984 [Csd]: Response header sent as 302 despite being set to 301
- #39984 [Csd->Opn]: Response header sent as 302 despite being set to 301
- #39984 [Opn->Asn]: Response header sent as 302 despite being set to 301
- #39984 [Asn]: Response header sent as 302 despite being set to 301
- #39984 [Asn->Sus]: Response header sent as 302 despite being set to 301
- #39984 [Sus]: Response header sent as 302 despite being set to 301
- #39984 [Sus]: Response header sent as 302 despite being set to 301
- #39984 [Sus]: Response header sent as 302 despite being set to 301
- #39984 [Com]: Response header sent as 302 despite being set to 301
| « previous | php.bugs (#109400) | next » |
|---|