Error 500 on /direct_messages/new

[er...@hammer-lahav.net]

No matter which format I use, I always get this. I am using a valid
username to send the message to. Sending the same message to the same
user via the web works well.

Thanks!

EHL

POST /direct_messages/new.xml HTTP/1.1
Authorization: Basic xxxxxxxxxxMg==
Connection: Close
Host: twitter.com
text: Hello
user: username

HTTP/1.1 500 Internal Server Error
Cache-Control: no-cache
Connection: close
Content-Length: 16
Content-Type: text/html; charset=utf-8
Date: Tue, 22 May 2007 18:03:36 GMT
Server: Joyent Web
Set-Cookie: _twitter_session=c9f325801bc2d2764b9a43ebb4da5326;
domain=.twitter.c
om; path=/
Status: 500 Internal Server Error
X-Runtime: 0.16101

[Cameron Kaiser]

> No matter which format I use, I always get this. I am using a valid
> username to send the message to. Sending the same message to the same
> user via the web works well.

If this was this morning, it might have had something to do with the
"Snafu!" 500 messages I was seeing in TTYtter.

--
------------------------------------ personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * cka...@floodgap.com
-- Rational behavior is a choice, not a predestination. -- Kent Paul Dolan ----

[Eran Hammer-Lahav]

This is still going on today. I get mostly 500, and sometimes 302.
Every once in a while the server also disconnects without a reply.

EHL

[Eran Hammer-Lahav]

Can someone confirm that they are able to use the direct message API
to send messages?

Many thanks,

EHL

[Eran Hammer-Lahav]

[Eran Hammer-Lahav]

Many thanks,

EHL