Expectation failed error 203

jbrohan · Post by **jbrohan** » Sat Aug 01, 2009 12:02 pm

HTTP/1.1 417 Expectation failed - http://www.teleuroflow.com/web/TUFcatchmessagetest.php
DocumentParser::FetchBuffer - could not open URL: TUFcatchmessagetest.php
DocumentParser::FetchDocument - exiting with error result 2
errno: 203 uri TUFcatchmessagetest.php

I keep getting this error when my xml script submits to this php file.

<catch event="connection.disconnect">
<submit next="TUFcatchmessagetest.php"
method="post" enctype="multipart/form-data"
namelist="myrecording urgency customerid "/>
</catch>

The galling part of this error is that it used to work and I made some minor change and now it's failing.

Any help most welcome
John

support · Post by **support** » Mon Aug 03, 2009 9:38 am

Hello,

We were able to get a more detailed trace of the HTTP request to your IVR server. The IVR error appears to be coming from a squid proxy on your side. Here is the trace to help you debug the IVR issue on your end.

Code: Select all

$ curl -v -F "myrecording=@myrecording;type=audio/basic&urgency=1&customerid=1234" http://www.teleuroflow.com/web/TUFcatchmessagetest.php

* About to connect() to www.teleuroflow.com:80
* Connected to 208.94.117.29 port 80
> POST /web/TUFcatchmessagetest.php HTTP/1.1
User-Agent: curl/7.10.6 (i686-redhat-linux-gnu) libcurl/7.10.6 OpenSSL/0.9.7a ipv6 zlib/1.1.4
Host: www.teleuroflow.com
Pragma: no-cache
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*
Content-Length: 480279
Expect: 100-continue
Content-Type: multipart/form-data; boundary=----------------------------01b031028b59

< HTTP/1.1 417 Expectation failed
< Server: squid/2.7.STABLE6
< Date: Mon, 03 Aug 2009 14:36:59 GMT
< Content-Type: text/html
< Content-Length: 1607
< X-Squid-Error: ERR_INVALID_REQ 0
< Connection: close
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>ERROR: The requested URL could not be retrieved</TITLE>
<STYLE type="text/css"><!--BODY{background-color:#ffffff;font-family:verdana,sans-serif}PRE{font-family:sans-serif}--></STYLE>
</HEAD><BODY>
<H1>ERROR</H1>
<H2>The requested URL could not be retrieved</H2>
<HR noshade size="1px">
<P>
While trying to process the request:
<PRE>
POST /web/TUFcatchmessagetest.php HTTP/1.1
User-Agent: curl/7.10.6 (i686-redhat-linux-gnu) libcurl/7.10.6 OpenSSL/0.9.7a ipv6 zlib/1.1.4
Host: www.teleuroflow.com
Pragma: no-cache
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*
Content-Length: 480279
Expect: 100-continue
Content-Type: multipart/form-data; boundary=----------------------------01b031028b59

</PRE>
<P>
The following error was encountered:
<UL>
<LI>
<STRONG>
Invalid Request
</STRONG>
</UL>

<P>
Some aspect of the HTTP Request is invalid.  Possible problems:
<UL>
<LI>Missing or unknown request method
<LI>Missing URL
<LI>Missing HTTP Identifier (HTTP/1.0)
<LI>Request is too large
<LI>Content-Length missing for POST or PUT requests
<LI>Illegal character in hostname; underscores are not allowed
</UL>
<P>Your cache administrator is <A HREF="mailto:support@nearlyfreespeech.net">support@nearlyfreespeech.net</A>.

<BR clear="all">
<HR noshade size="1px">
<ADDRESS>
Generated Mon, 03 Aug 2009 14:36:59 GMT by vhost.phx7.nearlyfreespeech.net (squid/2.7.STABLE6)
</ADDRESS>
</BODY></HTML>
* Closing connection #0

Regards,
Plum Support

jbrohan · Post by **jbrohan** » Mon Aug 03, 2009 12:22 pm

The guys at Nearly Free Speech tell me..."See if you can get whatever-the-client-is to stop issuing the Expect: header.

I think we can make a config change that will cause it to be ignored by the part of the system that's currently 417'ing it, but it really doesn't belong there." and then an hour later "The change I was referring to has been made, so this might work better now. (But it is still broken behavior.)"

Obviously I'm not knowledgeable enough to join in this discussion, but it's now working fine (phew!) thanks everyone.
John

Plum IVR Support

Expectation failed error 203

Expectation failed error 203

IVR debug of error 203