#26440 [Bgs->Opn]: headers not passed in stream context
| From: | steven at pearavenue dot com | Date: | Fri, 28 Nov 2003 18:17:48 +0000 |
| Subject: | #26440 [Bgs->Opn]: headers not passed in stream context | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-51238@lists.php.net to get a copy of this message | ||
ID: 26440
User updated by: steven at pearavenue dot com
Reported By: steven at pearavenue dot com
-Status: Bogus
+Status: Open
Bug Type: HTTP related
Operating System: Linux
PHP Version: 4.3.4
Assigned To: pollita
New Comment:
This bug continues and is not bogus
Previous Comments:
------------------------------------------------------------------------
[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
------------------------------------------------------------------------
[2003-11-28 13:06:26] steven at pearavenue dot com
This 5.0 error suggests an error in the resource creation that is not
reported by the fopen.
------------------------------------------------------------------------
[2003-11-28 13:05:07] iliaa@php.net
Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to
report
a bug at http://bugs.php.net/how-to-report.php
The reason that functions using $fp subsequent to fopen() fails is
because fopen() itself had failed and $fp === false.
------------------------------------------------------------------------
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