ID: 26440 User updated by: steven at pearavenue dot com Reported By: steven at pearavenue dot com Status: Closed Bug Type: HTTP related Operating System: Linux PHP Version: 4.3.4 Assigned To: pollita New Comment:
My thanks. I will confirm with the latest snap. Someone should document this 304 behavior - it is very useful. Previous Comments: ------------------------------------------------------------------------ [2003-11-28 13:49:55] [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. PHP4 was missing certain context features that prevented it from sending any context headers other then user_agent. This is now fixed. Now in both PHP5 & PHP4 fopen() fails due to 304 response code. ------------------------------------------------------------------------ [2003-11-28 13:17:48] steven at pearavenue dot com This bug continues and is not bogus ------------------------------------------------------------------------ [2003-11-28 13:15:40] steven at pearavenue dot com In the 4.3 snap fopen succeeds but does not produce the desired result. ------------------------------------------------------------------------ [2003-11-28 13:13:42] steven at pearavenue dot com I lied. false is returned by fopen. However, fopen succeeds without the context and fails with it. ------------------------------------------------------------------------ [2003-11-28 13:08:07] steven at pearavenue dot com I test for the error - the resource creation returns true from fopen ------------------------------------------------------------------------ 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
