Why does Twitter reject the Expect: 100-continue header in HTTP requests
with this self-contradictory response?

HTTP/1.1 417 Expectation Failed
Date: Mon, 11 Jan 2010 02:22:10 GMT
Server: hi
Vary: Accept-Encoding
Content-Length: 364
Connection: close
Content-Type: text/html; charset=iso-8859-1

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>417 Expectation Failed</title>
</head><body>
<h1>Expectation Failed</h1>
<p>The expectation given in the Expect request-header
field could not be met by this server.</p>
<p>The client sent<pre>
   * Expect: 100-continue*
</pre>
but we only *allow the 100-continue *expectation.</p>
</body></html>


--
Andrew Arnott
"I [may] not agree with what you have to say, but I'll defend to the death
your right to say it." - S. G. Tallentyre

Reply via email to