#24916 [Com]: IIS6.0 & CGI PHP header()
| From: | jeff at mos dot org | Date: | Tue, 19 Aug 2003 22:33:37 +0000 |
| Subject: | #24916 [Com]: IIS6.0 & CGI PHP header() | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-46263@lists.php.net to get a copy of this message | ||
ID: 24916
Comment by: jeff at mos dot org
Reported By: sadun at isikun dot org
Status: Bogus
Bug Type: IIS related
Operating System: Windows Server 2003
PHP Version: 4.3.2
New Comment:
I see that this has been marked 'bogus', but I think that there is
something going on.
I'm running PHP 4.3.2 on IIS 5.0 with FastCGI (isapi module version 0.6
from here:
http://www.caraveo.com/fastcgi/
My redirects (setting the header Location) were not working on Safari
when using https.
I looked at the headers from the page with wget and here is an excerpt
of what I see:
1 HTTP/1.1 302 Moved
2 Server: Microsoft-IIS/5.0
3 Date: Tue, 19 Aug 2003 22:05:29 GMT
4 (null)
5 Content-type: text/html
6 X-Powered-By: PHP/4.3.2
7 Location: http://ecomdev.mos.org/?action=showorder
Note that (null) line. What is that? An extra line feed or carriage
return?
I did not see the (null) line when running under ISAPI, but ISAPI is
not an option right now.
I made that mysterious (null) line go away, thus solving the Safari
issue, by setting this in php.ini:
cgi.rfc2616_headers = 0
I had it set to 1 originally.
So there you have it. Something is up.
Previous Comments:
------------------------------------------------------------------------
[2003-08-05 10:45:24] sniper@php.net
Please stop reopening this, there is no bug.
(ask support for this kind of obvious configuration errors elsewhere,
like php-general@lists.php.net for example)
------------------------------------------------------------------------
[2003-08-05 01:16:37] sadun at isikun dot org
INET_E_REDIRECT_FAILED is kind of an error that exe can cause. for more
information look at TechNET
"INET_E_REDIRECT_FAILED (0x800C0014L) -2,146,697,196 Attempt to
redirect the navigation failed."
the case is simple. login form action goes to main.php and if login is
correct it sets SESSION and COOKIE then it redirects user to main.php.
After redirection (which is need to set cookies) main.php checks users
cookie and sessions if they are valid bla bla bla....
as you seee there are no loop in redirections. there is only one
redirection which is done in main.php for one to set cookies. and if it
is not a bug why isapi module works well ???
i wish you could fix it. cause we are waiting for this debug. we can't
change all authentication for one redirection bug for spesific
combination.
------------------------------------------------------------------------
[2003-08-04 20:25:00] iliaa@php.net
Sorry, but your problem does not imply a bug in PHP itself. For a
list of more appropriate places to ask for help using PHP, please
visit http://www.php.net/support.php as this bug system
is not the
appropriate forum for asking support questions.
Thank you for your interest in PHP.
It would seem to me that if you make a redirect loop that the webserver
may detect such an occurance and throw an error as it happens in your
case. This is hardly a PHP bug.
------------------------------------------------------------------------
[2003-08-04 13:55:40] sadun at isikun dot org
i forgot to pick Status Open :)
still have the problem which is at the top...
------------------------------------------------------------------------
[2003-08-04 12:25:32] sadun at isikun dot org
I FOUND THE PROBLEM IF YOU REDIRECT USER TO SAME PHP FILE IT MAKES AN
ERROR LOOP.
let's say i execute a code at main.php and if i redirect user to
main.php you can see in the headers that it makes a loop with errors at
headers with "INET_E_REDIRECT_FAILED" but you can redirect anywhere
else except same file...
CODE
---------------------
<?
header("Location: http://webgroup.isikun.edu.tr/arge/header.php");
?>
ERROR AT HEADERS
---------------------
20:15:48.279 0.109 * GET INET_E_REDIRECT_FAILED text/html http://webgroup.isikun.edu.tr/arge/header.php
------------------------------------------------------------------------
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/24916
--
Edit this bug report at http://bugs.php.net/?id=24916&edit=1