sendsms HTTP 202 status response

Hi list,

I would like to ask about 202 status response with is returned by /cgi-bin/sendms when passing
proper parameters using GET method. here is what 202 is used for:

---
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. 
--
everything is OK execpt using some "user-friendly" languages, such as php. for example, putting the whole sendsms URL
into include() function produces the following warnings:

Warning: main(http://xxx:13013/cgi-bin/sendsms?user=test&pass=testing&to=xxx&from=xxx&udhtext=test&smsc=xxx) [function.main]: failed to create stream: HTTP request failed! HTTP/1.0 202 Foo in /var/www/xxx/test.php on line 100

Warning: main() [function.main]: Failed opening 'http://xxx:13013/cgi-bin/sendsms?user=test&pass=testing&to=xxx&from=xxx&&text=test&smsc=xxx for inclusion (include_path='.:/usr/local/lib/php') in /var/www/xxx/test.php on line 100

if require() is used instead of include(), GET request is passed (SMS is sent), but script will die (due to require() semantics). 

shouldn't be repsonse changed into "normal", i.e. 200? 

regards,
Dziugas Baltrunas