[twitter-dev] Re: OAuth POST gets 401 with no data/error message returned
Is this issue perhaps related to the one I raised two days ago? http://bit.ly/9dG7jk On Mar 12, 4:55 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Can you present an example of you POSTing to a resource? An example signature base string of what you're trying to accomplish and the example POST body you are sending? Thanks! Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Fri, Mar 12, 2010 at 12:22 PM, SM sanja...@gmail.com wrote: My desktop app uses Adobe AIR with Javascript. I'm using the OAuth javascript library from here: http://oauth.googlecode.com/svn/code/javascript/ I am able to POST with xAuth to get the token/token_secret. I am then able to GET timelines using the received tokens. However, so far I am unable to POST to send updates or create/destroy favorites. When I compare the Authorization header my code generates with the one you can generate manually at this site: http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin... they are identical. Nevertheless, I am getting a 401 status back but no JSON data telling me what the error is. First question: any idea what might be going on here? Second question: Under what conditions would one get a 401 status, but no data describing the error? Stumped!
[twitter-dev] Re: OAuth POST gets 401 with no data/error message returned
Hi Taylor, Here is an example of trying to create a favorite on status 10390395026. Here is the base string: POSThttps%3A%2F%2Fapi.twitter.com%2F1%2Ffavorites%2Fcreate %2F10390395026.jsonid%3D10390395026%26oauth_consumer_key %3DoVpGXZGmqq7NyScJTLd7Xg%26oauth_nonce %3DogJ8y0%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp %3D1268428713%26oauth_token%3D10881- YdTJEhpXTBk2NJyg3juPXV8rq05jfGLp6HA1rk6MvI%26oauth_version%3D1.0 Here is the Authorization header: OAuth realm=,oauth_version=1.0,oauth_signature_method=HMAC- SHA1,oauth_nonce=ogJ8y0,oauth_token=10881- YdTJEhpXTBk2NJyg3juPXV8rq05jfGLp6HA1rk6MvI,oauth_timestamp=1268428713,oauth_signature=4EM %2FeX8xCFnW77zWtTTKFQoftaQ %3D,oauth_consumer_key=oVpGXZGmqq7NyScJTLd7Xg The POST body is just: id=10390395026 The URL is: https://api.twitter.com/1/favorites/create/10390395026.json Thanks. On Mar 12, 12:55 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Can you present an example of you POSTing to a resource? An example signature base string of what you're trying to accomplish and the example POST body you are sending? Thanks! Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Fri, Mar 12, 2010 at 12:22 PM, SM sanja...@gmail.com wrote: My desktop app uses Adobe AIR with Javascript. I'm using the OAuth javascript library from here: http://oauth.googlecode.com/svn/code/javascript/ I am able to POST with xAuth to get the token/token_secret. I am then able to GET timelines using the received tokens. However, so far I am unable to POST to send updates or create/destroy favorites. When I compare the Authorization header my code generates with the one you can generate manually at this site: http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin... they are identical. Nevertheless, I am getting a 401 status back but no JSON data telling me what the error is. First question: any idea what might be going on here? Second question: Under what conditions would one get a 401 status, but no data describing the error? Stumped!
[twitter-dev] Re: OAuth POST gets 401 with no data/error message returned
Taylor, Under what circumstances does your system return a 401 HTTP status code but does not include a properly formed XML or JSON error construct to explain the 401? Find that, and I think you will find the problem. On Mar 12, 4:22 pm, SM sanja...@gmail.com wrote: My desktop app uses Adobe AIR with Javascript. I'm using the OAuth javascript library from here: http://oauth.googlecode.com/svn/code/javascript/ I am able to POST with xAuth to get the token/token_secret. I am then able to GET timelines using the received tokens. However, so far I am unable to POST to send updates or create/destroy favorites. When I compare the Authorization header my code generates with the one you can generate manually at this site: http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin... they are identical. Nevertheless, I am getting a 401 status back but no JSON data telling me what the error is. First question: any idea what might be going on here? Second question: Under what conditions would one get a 401 status, but no data describing the error? Stumped!
