Hi there,
If you look at the Google Code issue [1] you'll see the questions
I asked in comment #2. Without that basic information I can't provide
any sort of help. Our logs, as you can imagine, are large. So just
looking for a single request is like looking for a needle in a pile of
needles. There was a second Google Code issue [2] where we discussed
some signature issues, and that might also be helpful. We can review
that if we need to, but for now the questions from the first issue [1]
would be helpful … please fill them in at:
http://code.google.com/p/twitter-api/issues/entry?template=OAuth%20Issue
Thanks;
— Matt Sanford
[1] - http://code.google.com/p/twitter-api/issues/detail?id=447#c2
[2] - http://code.google.com/p/twitter-api/issues/detail?id=433
On Apr 18, 2009, at 05:26 PM, meatwad wrote:
I'm having the same problems.
Doing a POST to...
https://twitter.com/statuses/update.xml
POST data..
oauth_version=1.0
oauth_nonce=d4afc59eae1eda82d4efb0c871608256
oauth_timestamp=1240100668
oauth_consumer_key=MY_CONSUMER_KEY
status=Hello+World%21
oauth_token=OAUTH_TOKEN_FOR_USER
oauth_signature_method=HMAC-SHA1
oauth_signature=SW%2F9aNwK6HvNS6NblzezTK8iJj0%3D
Error:
"Failed to validate oauth signature or token"
On Apr 11, 1:09 pm, Dominik Schwind <domi...@gmail.com> wrote:
On Sat, Apr 11, 2009 at 6:40 PM, jmathai <jmat...@gmail.com> wrote:
Here's a bug for the
problem:http://code.google.com/p/twitter-api/issues/detail?id=447
K, thx, I answered the questions there, I hope it helps. :)
