[twitter-dev] Re: Statuses/destroy is returning 400 even though tweet is deleted sucessfully

+1 - I am experiencing the same problem. I'm running Twitter API requests as part of a unit test for my code (HTTPBuilder- http://groovy.codehaus.org/modules/http-builder/). This has always worked fine up until a couple weeks ago. Looks like there is a bug report here: http://code.google.com/p/

POST, Expect header, and Apache HttpClient (Java)

There is a similar issue when using Apache HttpClient (a common HTTP framework for Java). It appears that POST requests will automatically add an Expect: 100-Continue header. And I suspect this is failing because HttpClient does not attempt to send auth credentials until first challenged by a 40

[twitter-dev] Accept header and OPTIONS method

Two questions: 1. Could the REST API use the Accept header rather than looking for the content-type in the URL? i.e. instead of doing: http://twitter.com/statuses/public_timeline.json do this: http://twitter.com/statuses/public_timeline with an Accept: application/json header? I understand yo