Thanks Jake, I was getting the same errors. Is this expected behavior now for Twitter or is this a bug in the new Twitter release (Not supporting the Expect: Continue header). I'm writing a multi-service Windows Mobile application and I'd prefer not changing global http connection settings if I don't have to.
> Thanks for helping out with this tip, Jake. > > On Tue, Dec 23, 2008 at 20:31, JakeS <jakesteven...@gmail.com> 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. > > -- > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
