#9852 [Com]: Header redirect and db connection cause "CGI misbehaved"
| From: | scott at datalink dot net dot au | Date: | Mon, 05 Aug 2002 02:48:51 +0000 |
| Subject: | #9852 [Com]: Header redirect and db connection cause "CGI misbehaved" | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-15985@lists.php.net to get a copy of this message | ||
ID: 9852
Comment by: scott@datalink.net.au
Reported By: ron.baldwin@sourceprose.com
Status: Closed
Bug Type: IIS related
Operating System: Windows 2000
PHP Version: 4.2.1
New Comment:
Here's a reason to open this bug: If PHP worked properly with
enterprise products we would consider using it for enterprise
solutions.
How can you state that there is nothing solid to go on, considering the
opening bugnote begins with: "Under the category of 'You Can Never Have
Too Much Information On A Bug'", and this bug has over 600 lines of
descriptive information, including step-by-step procedures and scripts
to reproduce it!
Regardless of who is to blame (IIS, MSSQL, PHP, Solar Flares), the bug
exists anyway, and it is in the interest of PHP to track it.
By closing this bug because somebody claimed that a MDAC upgrade *may*
solve the problem is wrong. If all bugs were handled using hearsay I
would not feel comfortable about the quality of PHP in general. How
about having someone who can replicate this bug become responsible for
it, and only when they are happy should the bug be closed.
I am happy to become this person, to help improve the quality of the
PHP codebase and the support team.
In the meantime, please re-open this bug.
Previous Comments:
------------------------------------------------------------------------
[2002-07-15 11:48:06] rasmus@php.net
There is really nothing solid to go on here. Everything points to an
IIS issue, and as mentioned upgrading MDAC seems to fix it, so unless
there is some real evidence that this is something we can fix at the
PHP level, I see no reason for this to be an open bug in the PHP bug
database.
------------------------------------------------------------------------
[2002-07-15 11:31:14] ottawasixtyseven@hotmail.com
Just wondering if the PHP dudes read the comments in the "closed" bugs.
I agree that this bug should NOT be closed! Servers are getting faster
and faster and this bug seems to happen more often on faster machines.
It's going to become a real nightmare soon. Too bad the ISAPI module is
so buggy that we're forced to use CGI mode. Maybe we should re-open
this bug. How do you do that?
------------------------------------------------------------------------
[2002-07-10 12:42:44] wrichard@mail.com
How can this possibly be closed? The bug is *still* there even in the
latest snap that was supposed to fix it...
The arrogance astounds me.... This is a very annoying problem
that needs to go away, regardless of M$ or not.
------------------------------------------------------------------------
[2002-06-26 18:54:24] davidr@gronks.com
I did find that upgrading the VBScripting engine and MDAC to 2.7RTM
seemed to resolve the problem. Well, not sure about resolving but the
error hasn't occured since.
------------------------------------------------------------------------
[2002-06-21 03:10:26] davidr@gronks.com
I have found that by removing anonymous IUSR permissions on the web
site and then logging into the web site using an administrators
creditonals that the error will not occur.
The error will also not occur if the web sites anonymous user is set to
run as a user that has local Administrator privledges.
------------------------------------------------------------------------
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/9852
--
Edit this bug report at http://bugs.php.net/?id=9852&edit=1