W3C home > Mailing lists > Public > www-voice@w3.org > January to March 2007

response codes for non-http protocols in error.badfetch.protocol.responsecode generation under VXML 2.1

From: David Nicol <davidnicol@gmail.com>
Date: Thu, 22 Mar 2007 18:00:14 -0600
Message-ID: <934f64a20703221700x1a5e78d2u331e071fdfad2a32@mail.gmail.com>
To: www-voice@w3.org

error.badfetch.http.response_code
error.badfetch.protocol.response_code
    In the case of a fetch failure, the interpreter context must use a
detailed event type telling which specific HTTP or other
protocol-specific response code was encountered. The value of the
response code for HTTP is defined in [RFC2616]. This allows
applications to differentially treat a missing document from a
prohibited document, for instance. The value of the response code for
other protocols (such as HTTPS, RTSP, and so on) is dependent upon the
protocol.


How widely implemented are non-http response codes?  For instance, DNS really
doesn't have response codes as such -- should one fake the proxy
return codes from
DNS errors?


-- 
"When the day comes that anyone can bend our country's laws and
lawmakers to serve selfish, competitive ends, that day democratic
government dies. And we're just optimistic enough to believe that once
the facts are on the table, American public opinion will walk in with
a big stick." -- Preston Tucker, June 15, 1948
Received on Friday, 23 March 2007 00:00:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 23 March 2007 00:00:20 GMT