ID: 21637
User updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: IIS related
Operating System: Windows 2000
PHP Version: 4.3.0
New Comment:
It was working fine with PHP up to version 4.2.2 (dont know about 4.2.3
because of our ohter problem with headers cf bug #19351)
Previous Comments:
------------------------------------------------------------------------
[2003-01-16 09:30:46] [EMAIL PROTECTED]
sure, it should not crash or hang, but...
this combination of header fields just makes no sense,
as the actual content-type is determined by the result
of the request to the 'Location:' URL
(right now i can't think of *any* header that would
make sense in combination with 'Location:')
maybe it is even the webserver itself and not php
that gets confused by this header combination?
did it work with previous PHP versions?
------------------------------------------------------------------------
[2003-01-15 12:49:48] [EMAIL PROTECTED]
php4isapi.dll created friday the 27th of december 2002 at 05:43:24.
We even created a filter at the master properties level of IIS using
php4isapi.dll. It used to fix a lot of "memory" problems...
------------------------------------------------------------------------
[2003-01-15 12:37:17] [EMAIL PROTECTED]
Which SAPI are you using?
------------------------------------------------------------------------
[2003-01-15 08:00:54] [EMAIL PROTECTED]
Actually, there is no error, the system just stalls, we got nothing out
as a result and we are forced to kill the inetinfo process to restart
PHP (just stopping the service W3SVC wont work, the service wont
stopped and will stay in a "stopping" mode). It seems to be a problem
between IIS and PHP, but we didn't have this problem up to version
4.2.2. We had another problem with the headers in version 4.2.3 that
was reported in bug #19351, maybe it is related?
------------------------------------------------------------------------
[2003-01-14 19:20:36] [EMAIL PROTECTED]
What do you mean with 'crash' ? Do you get any errors?
------------------------------------------------------------------------
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/21637
--
Edit this bug report at http://bugs.php.net/?id=21637&edit=1
