Bug #9846 Updated: fopen() fails and gives Error 0 on NoContent URLs

ID: 9846 Updated by: sander Reported By: bloch@incrementalimages.com Old Status: Feedback Status: Closed Bug Type: Filesystem function related Operating System: linux,irix,tru64 PHP Version: 4.0.4pl1 New Comment: No feedback. Closing. Previous Comments: ------------------------------------------------------------------------ [2001-11-23 18:03:19] venaas@php.net Doesn't the contents of $http_response_header tell you what you need? $http_response_header should be an array of the HTTP response fopen() got ------------------------------------------------------------------------ [2001-10-29 02:35:13] sniper@php.net Taken from #9847, these are basically the same problem: When fopen()-ing an URL that responds with an HTTP 403 Forbidden, fopen() fails with an Error 0. There is no way to distinguish this error from a 'Not Found' type of error. --- ------------------------------------------------------------------------ [2001-03-19 16:56:02] bloch@incrementalimages.com This bug might belong in the URL-related section. I believe it to be a generic problem. If you fopen() an URL that returns with an HTTP Header of NoContent (204), fopen() will fail with Error 0. Failure would be ok if there was a specific error code for NoContent URLs. Either that or returning a handle that was already at eof would suffice. As it is now, there's no way to tell the difference between a bad (NotFound) URL and a NoContent URL. Work-around it to use cURL to a temporary file and check the HTTP_CODE with the undocumented curl_getinfo() function. Of course, it seems a little weird to require the temporary file for a NoContent URL. But it works fine. -Eric Bloch bloch@incrementalimages.com ------------------------------------------------------------------------ Edit this bug report at http://bugs.php.net/?id=9846&edit=1