error.badfetch.{protocol}.{response code}

This event is a special case of the error.badfetch event. Specifically, it applies to the case where the Voice Browser service attempts to fetch a resource through a standard protocol such as HTTP, and fails. In a case such as this, the Voice Browser service throws a detailed event name. This feature allows developers to provide custom handling in a protocol-specific and/or response code specific manner, for example:

<!--Handle all errors resulting from an internal server error when fetching resources (<grammar>s, documents,<audio>s, etc.)-->

<catch event="error.badfetch.http.500">

    <prompt>

      Sorry, but our web server is having problems.Please try again later.

    </prompt>

    <exit/>

</catch>

Or:

<!-- Catch all errors having to do with HTTPS, redirecting the user to the insecure version of this page.

Keep in mind that the actual event name is the fully qualified 'error.badfetch.https.300' etc., but using the standard VoiceXML event handling framework, we are clustering all such events into one handler.

-->

<catch event="error.badfetch.https">

    <prompt> Sorry, but our secure site is having some problems.

        Taking you to the insecure version.

    </prompt>

    <exit/>

</catch>

The response codes for each protocol are defined in their respective Request for Comments (RFC) published by the Network Working Group of the Internet Engineering Task Force. See RFC 2616 for information on HTTP response codes.