I'm currently getting 417 as well on my php from script using curl
Sent from my iPhone
On 24 Dec 2008, at 23:50, "dean.j.robinson"
<[email protected]> wrote:
Started getting reports from users yesterday that they couldn't login
to hahlo.com.
Turns out that the check I run against "verify credentials" was also
returning code 417 instead of the usual/expected 200, so even though
the check was working to hahlo is looked like it was failing, changed
my check to include code 417 and now its working again.
Strangely though, a local dev copy of Hahlo 4, which also checks
"verify credentials" and also only expects a 200 response, is still
working fine..,
On Dec 25, 6:57 am, Tom Morris <[email protected]> wrote:
On Dec 24, 4:31 am, JakeS <[email protected]> wrote:
Looks like twitter is updating something and their servers are
returning error 417 for a lot of requests. I looked into it and
found
that .NET automatically includes an Expect header containing "100-
continue" on every request unless you specifically tell it not to.
So for any .NET devs having trouble, you can set
System.Net.ServicePointManager.Expect100Continue = false before
making
your request to get past this issue.
A lot of libraries follow this behaviour. A Twitter app I wrote in
PHP
a while back has been logging 417s most of today. I logged in and
added:
curl_setopt($ch, CURLOPT_HTTPHEADER, array('Expect:'));
Other libcurl-based libraries may be affected. There are plenty of
reports about 417 and Expect on the cURL website -http://
curl.haxx.se/
- and on the websites of particular language bindings.
--
Tom Morris (@tommorris)
<http://tommorris.org>
