Looking at some of your example debug output above, you're sending a Content-Type header of text/xml when you aren't sending us XML, you're sending us x-www-form-urlencoded data.
Taylor On Wed, Sep 1, 2010 at 7:38 AM, Papa.Coen <papa.c...@gmail.com> wrote: > And now for something strange: > > I get the same 500 response _regardless_ of what I put in the body. > Also when the data in the Signature base string is different from what > is used in the body. So not even a '401 unauthorized' message... > > At first I suspected the(/my) signature, but now I have doubts. Lots > of them. And still no solution... > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
