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%3DI1yQDPyI7WUn2fN9JfFWww
%26oauth_nonce%3DzUiSrxqbsHQDdLL808dHSGwK1SJT78RKA7q266lQtms%253D
%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
%3D1283329212%26oauth_token%3D172686984-
rnCFtLBbV00YlZVXN0Um1weBPk1dZ3sQXh22rTkG%26oauth_version%3D1.0%26status
%3Dsetting%2520up%2520my%2520twitter%2520hoot

Sniffed:

POST /1/statuses/update.json HTTP/1.1
Content-Type: text/xml; charset=utf-8
User-Agent: RTL Netherlands OAuth 0.1
Authorization: OAuth oauth_consumer_key="I1yQDPyI7WUn2fN9JfFWww",
oauth_signature_method="HMAC-SHA1", oauth_timestamp="1283329212",
oauth_nonce="zUiSrxqbsHQDdLL808dHSGwK1SJT78RKA7q266lQtms%3D",
oauth_version="1.0", oauth_token="172686984-
rnCFtLBbV00YlZVXN0Um1weBPk1dZ3sQXh22rTkG", oauth_signature="GjVUXM%2Fw
%2FhlIoC5BuFQSSqnkRSU%3D"
Host: api.twitter.com
Content-Length: 41
status=setting%20up%20my%20twitter%20hootHTTP/1.1 500 Internal Server
Error
Date: Wed, 01 Sep 2010 08:20:44 GMT

Server: hi
Status: 500 Internal Server Error
Content-Type: text/html; charset=UTF-8
Set-Cookie: k=217.118.160.30.1283329243822931; path=/; expires=Wed, 08-
Sep-10 08:20:43 GMT; domain=.twitter.com
Cache-Control: max-age=300
Expires: Wed, 01 Sep 2010 08:25:43 GMT
Vary: Accept-Encoding
Connection: close
Transfer-Encoding: chunked
f4
Status: 500 Internal Server Error
Content-Type: text/html
<html><body><h1>500 Internal Server Error</h1></body></html>Status:
500 Internal Server Error
Content-Type: text/html
<html><body><h1>500 Internal Server Error</h1></body></html>
0

-- 
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

Reply via email to