Thank you for your support. I saw you message a little too late, but
was indeed the problem!
Again: thanks a bunch.
Coen
On Sep 1, 5:00 pm, Taylor Singletary
wrote:
> Looking at some of your example debug output above, you're sending a
> Content-Type header of text/xml when you aren't sending
Fixed!
CONTENT TYPE must be: "application/x-www-form-urlencoded" ! 1337.
Thanks to this post:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/2c84b962327f7161/7d5e1fd98644913e?lnk=gst&q=internal+server+error#7d5e1fd98644913e
--
Twitter developer documentation and re
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 wrote:
> And now for something strange:
>
> I get the same 500 resp
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
FYI:
- I'm hailing to Twitter via C#
- If I send the data in my request chunked, I get a different error
message:
HTTP/1.1 500 Internal Server Error
Date: Wed, 01 Sep 2010 13:02:53 GMT
Server: Apache
Set-Cookie: k=217.118.160.30.1283346173979846; path=/; expires=Wed, 08-
Sep-10 13:02:53 GMT; domai
At first I was like:
Oh Noos!
But then I was like:
I changed my code to URL encode the body data, but still get the 500.
I get this for _every_ update request I make.
Signature base string:
POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses
%2Fupdate.json&oauth_consumer_key%3DI1yQDPyI7WUn2fN9JfFWw