Hi Jeremy,
Sorry for the delayed reply. The most helpful thing to send are
the request headers, response headers and response body. With that I
can generally troubleshoot most problems and none of it should be
proprietary since it is just a log of what you're sending to Twitter.
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
On Jun 22, 2009, at 12:57 PM, King Kovifor wrote:
Matt,
Sorry for the double post. :) But, basically, I am using Abraham's
OAuth class. What I am doing is getting a request URL and token,
saving the token to a database (using a vBulletin specific method --
that part at least works). By token I save both oauth_token and
oauth_token_secret. Basically the flow uses the same file, but checks
for a returned token. Upon that, I send an OAuth HTTP request to
https://www.twitter.com/statuses/update with a status parameter. The
debug code prints out the last HTTP request code, and all the keys and
tokens that I use. 500 showed up... Would you like to see the actual
file? As I will send it, but at least a few lines will be invisible or
confusing as it's vBulletin specific and illegal for me to send it.
Jeremy
On Jun 22, 11:56 am, Matt Sanford <[email protected]> wrote:
Hello,
It's a bit difficult to provide much help based on the
description below. Is it possible for you to provide the HTTP request
and response headers (both are important) for the request returning
HTTP 500? Given that information I can try and track down the request
and find the cause of the problem. Also, in the future please do not
double post to the the list. It slows down response times while we
all
process all of our incoming messages.
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
On Jun 21, 2009, at 8:32 PM, King Kovifor wrote:
OK, so I have been having troubles with my aplication. I'm new to
OAuth, so it's probably wrong somewhere on my end.
I got it so that it recognizes that the token is coming from my
application, so it takes me and says "Deny" or "Allow". So far, so
good. Ok. Clicking on Authorize, I get the "Redirecting you to the
application" notification, so it redirects. I do a test to send a
tweet, but it hasn't worked. So I threw in some debug code and I'm
getting an HTTP response of 500! Twitter's end apparently? And if I
check "Connections" the application that I authorized, IS NOT THERE.
Now, this is where I'm lost, on both... help?
