ID:               26440
 Updated by:       [EMAIL PROTECTED]
 Reported By:      steven at pearavenue dot com
-Status:           Open
+Status:           Feedback
 Bug Type:         HTTP related
 Operating System: Linux
 PHP Version:      4.3.4
 Assigned To:      pollita
 New Comment:

It works as expected here, what output do you get?


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

[2003-11-28 02:17:15] steven at pearavenue dot com

I checked the last two snapshots and do not see this fix - the example
behaves as before.

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

[2003-11-27 21:02:57] steven at pearavenue dot com

Can I get a 4.3.4 patch for this? I am a little nervous about using a
snapshot when I go into production.

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

[2003-11-27 19:11:01] steven at pearavenue dot com

Damn, that was quick. Well done.

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

[2003-11-27 18:59:43] [EMAIL PROTECTED]

This bug has been fixed in CVS.

In case this was a PHP problem, snapshots of the sources are packaged
every three hours; this change will be in the next snapshot. You can
grab the snapshot at http://snaps.php.net/.
 
In case this was a documentation problem, the fix will show up soon at
http://www.php.net/manual/.

In case this was a PHP.net website problem, the change will show
up on the PHP.net site and on the mirror sites in short time.
 
Thank you for the report, and for helping us make PHP better.

The memory leak is not fixed. After the fix the script works as
expected, fopen() fails because the return code is 304 (what you
wanted) and not 200.

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

[2003-11-27 18:37:32] steven at pearavenue dot com

It fails with HEAD too under the release 4.3.4. Thanks for confirming.

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

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/26440

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

Reply via email to