#23740 [NEW]: Incorrect behaviour resulting from HTTP Status Code 202

From: Date: Wed, 21 May 2003 16:23:41 +0000
Subject: #23740 [NEW]: Incorrect behaviour resulting from HTTP Status Code 202
Groups: php.bugs 
Request: Send a blank email to php-bugs+get-40141@lists.php.net to get a copy of this message
From: scoop at freshmeat dot net Operating system: Linux 2.4 PHP version: 4.3.1 PHP Bug Type: HTTP related Bug description: Incorrect behaviour resulting from HTTP Status Code 202 When using file() or other streams functions supporting the use of URIs as their parameter the function behaves incorrectly when encountering HTTP Status Code 202. It'd be useful to return the accessed document instead of returning nothing at all and issuing a warning since the document body is likely to include a reason why status code 202 is being returned (as suggested by the RFC). Would it be possible to change that behaviour? Thanks. Example: Warning: file(http://games.slashdot.org/games.rdf) [http://www.php.net/function.file]: failed to create stream: HTTP request failed! HTTP/1.1 202 Accepted Reference: The HTTP RFC 10.2.3 202 Accepted The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place. There is no facility for re-sending a status code from an asynchronous operation such as this. The 202 response is intentionally non-committal. Its purpose is to allow a server to accept a request for some other process (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the server persist until the process is completed. The entity returned with this response SHOULD include an indication of the request's current status and either a pointer to a status monitor or some estimate of when the user can expect the request to be fulfilled. -- Edit bug report at http://bugs.php.net/?id=23740&edit=1 -- Try a CVS snapshot: http://bugs.php.net/fix.php?id=23740&r=trysnapshot Fixed in CVS: http://bugs.php.net/fix.php?id=23740&r=fixedcvs Fixed in release: http://bugs.php.net/fix.php?id=23740&r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=23740&r=needtrace Try newer version: http://bugs.php.net/fix.php?id=23740&r=oldversion Not developer issue: http://bugs.php.net/fix.php?id=23740&r=support Expected behavior: http://bugs.php.net/fix.php?id=23740&r=notwrong Not enough info: http://bugs.php.net/fix.php?id=23740&r=notenoughinfo Submitted twice: http://bugs.php.net/fix.php?id=23740&r=submittedtwice register_globals: http://bugs.php.net/fix.php?id=23740&r=globals PHP 3 support discontinued: http://bugs.php.net/fix.php?id=23740&r=php3 Daylight Savings: http://bugs.php.net/fix.php?id=23740&r=dst IIS Stability: http://bugs.php.net/fix.php?id=23740&r=isapi Install GNU Sed: http://bugs.php.net/fix.php?id=23740&r=gnused

« previous php.bugs (#40141) next »