ID: 18901
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: No Feedback
+Status: Closed
Bug Type: IIS related
Operating System: Windows 2000
PHP Version: 4.2.0
New Comment:
The behaviour of returning status codes has been fixed in 4.3.0.
Previous Comments:
------------------------------------------------------------------------
[2002-09-15 01:00:01] [EMAIL PROTECTED]
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
------------------------------------------------------------------------
[2002-09-14 05:49:15] [EMAIL PROTECTED]
It's not caused by session_start. I replaced that with my own session
handler and still have the problem. It looks like you have to have
frames and be displaying in the browser on the desktop of the web
server to see it happen.
------------------------------------------------------------------------
[2002-09-08 15:52:01] [EMAIL PROTECTED]
PS. This is with the last few versions of PHP, I'm now on version
4.2.3 and I'm using php.exe
------------------------------------------------------------------------
[2002-09-08 15:38:28] [EMAIL PROTECTED]
I don't know if this is the exact same thing but - I get random CGI
ERROR ...not returning a complete set of headers errors as well. This
is on several Windows 2000 IIS 5.0 machines.
It only happens to my pages that are in frames and that do a
session_start(). It looks like the pages sometimes crash because of
fighting over access to the session data since both frames are
requested at almost the same time. The frameset never crashes and I
assume this is because it has to finish before the framed pages are
called. If you refresh each frame by hand after the errors happen,
each page executes OK.
Charlie
------------------------------------------------------------------------
[2002-08-14 11:50:05] [EMAIL PROTECTED]
Are you using php.exe or php4isapi.dll?
------------------------------------------------------------------------
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/18901
--
Edit this bug report at http://bugs.php.net/?id=18901&edit=1
