ID:          15885
 Updated by:  [EMAIL PROTECTED]
 Reported By: [EMAIL PROTECTED]
-Status:      Feedback
+Status:      Closed
 Bug Type:    Other web server
 PHP Version: 4.1.2
 New Comment:

The zero-size file problem was caused by a conflict of special values
between mmc and php.  The conflict has been resolved for some time.

The observed difference in expiring connections is true.  Note however
that the new behaviour conforms to RFC 2616.  Especially, section 8.1.4
states:

"A client, server, or proxy MAY close the transport connection at any
time. [..]

"This means that clients, servers, and proxies MUST be able to recover
from asynchronous close events. [..]


Previous Comments:
------------------------------------------------------------------------

[2002-11-04 15:34:54] [EMAIL PROTECTED]

Sorry, I don't remember that password after 8 months.
Hmm... file_address is still set to (char *)1... 
Anyway, it appears to be ok now.

But I noticed another difference between thttpd with and without
php4-latest. Plain thttpd 2.21b issues a 408 after exactly 1 minute
when the client has not sent any request. With php4-latest the
connection is just closed without any error and the time is sometimes
as short as 4 seconds. My 2.22beta4 with (patched) PHP 4.1.2 reacts
correctly like plain thttpd.

------------------------------------------------------------------------

[2002-11-03 11:07:44] [EMAIL PROTECTED]

Please try using this CVS snapshot:

  http://snaps.php.net/php4-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php4-win32-latest.zip



------------------------------------------------------------------------

[2002-03-05 12:59:34] [EMAIL PROTECTED]

PHP for thttpd sets TG(hc)->file_address = (char *)1 to mark a
connection as "don't close".
thttpd used this value to mark files without mapped memory (0 byte
files). When such a file is requested, the client hangs.


------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=15885&edit=1

Reply via email to