Re: [twitter-dev] Re: 401 errors calling access_token
* Taylor Singletary taylorsinglet...@twitter.com [100901 08:35]: I'll try to respond to you today. It's no excuse, I know, but we've been busy! :) *nudge* -- 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
Re: [twitter-dev] Re: 401 errors calling access_token
* Taylor Singletary taylorsinglet...@twitter.com [100827 11:11]: Can you provide any more details about the error response you're giving (like the actual body of the error response)? Taylor, I emailed the full HTTP request and response along with the request token/secret for one of these 401 errors we're seeing. Did you get that email? Did it shed any light on the problem? Although most token exchanges work without error, this happens frequently enough to be a real concern. New users are sometimes unable to register and we lose them forever. -Marc -- 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
Re: [twitter-dev] Re: 401 errors calling access_token
Hi Marc, I'll try to respond to you today. It's no excuse, I know, but we've been busy! :) Taylor On Wed, Sep 1, 2010 at 8:33 AM, Marc Mims marc.m...@gmail.com wrote: * Taylor Singletary taylorsinglet...@twitter.com [100827 11:11]: Can you provide any more details about the error response you're giving (like the actual body of the error response)? Taylor, I emailed the full HTTP request and response along with the request token/secret for one of these 401 errors we're seeing. Did you get that email? Did it shed any light on the problem? Although most token exchanges work without error, this happens frequently enough to be a real concern. New users are sometimes unable to register and we lose them forever. -Marc -- 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 -- 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
Re: [twitter-dev] Re: 401 errors calling access_token
* Taylor Singletary taylorsinglet...@twitter.com [100901 08:35]: I'll try to respond to you today. It's no excuse, I know, but we've been busy! :) Thanks, Taylor. -- 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
Re: [twitter-dev] Re: 401 errors calling access_token
Great, thanks. Just wanted to check. Matt On Mon, Aug 30, 2010 at 9:55 PM, Marc Mims marc.m...@gmail.com wrote: * Matt Harris thematthar...@twitter.com [100830 16:37]: Did you get a chance to send this information through to our support team? Yes, Matt. Instead of doing a list reply, I replied directly to Taylor Singletary with full request and response for a failure case and the saved response token/secret from session data. -Marc On Fri, Aug 27, 2010 at 5:16 PM, Marc Mims marc.m...@gmail.com wrote: * Taylor Singletary taylorsinglet...@twitter.com [100827 11:11]: Can you provide any more details about the error response you're giving (like the actual body of the error response)? Taylor, I will capture the full request and response. I assume they are not suitable for posting in a public forum. Should I email the to a...@twitter.com instead? Can you share an example of a signature base string and POST body that failed in this example? Have you verified that the clock on the device/system originating the request is in sync with Twitter's (returned in the Date header of every request) by about 5 minutes? Times are within 1 second. Do you have any successes to compare against? The error seems to occur infrequently. The vast majority of calls succeed on exactly the same code path. The calls are being made with Perl the Net::Twitter library (of which I am the author). Net::Twitter is used by many twitter apps and web apps. Are your HTTP methods in agreement between what your client is actually using (a GET) and the method declared in your signature base string? Yes. -Marc -- 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 -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- 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 -- 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 -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- 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
Re: [twitter-dev] Re: 401 errors calling access_token
Hi Marc, Did you get a chance to send this information through to our support team? Best, Matt On Fri, Aug 27, 2010 at 5:16 PM, Marc Mims marc.m...@gmail.com wrote: * Taylor Singletary taylorsinglet...@twitter.com [100827 11:11]: Can you provide any more details about the error response you're giving (like the actual body of the error response)? Taylor, I will capture the full request and response. I assume they are not suitable for posting in a public forum. Should I email the to a...@twitter.com instead? Can you share an example of a signature base string and POST body that failed in this example? Have you verified that the clock on the device/system originating the request is in sync with Twitter's (returned in the Date header of every request) by about 5 minutes? Times are within 1 second. Do you have any successes to compare against? The error seems to occur infrequently. The vast majority of calls succeed on exactly the same code path. The calls are being made with Perl the Net::Twitter library (of which I am the author). Net::Twitter is used by many twitter apps and web apps. Are your HTTP methods in agreement between what your client is actually using (a GET) and the method declared in your signature base string? Yes. -Marc -- 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 -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- 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
Re: [twitter-dev] Re: 401 errors calling access_token
* Matt Harris thematthar...@twitter.com [100830 16:37]: Did you get a chance to send this information through to our support team? Yes, Matt. Instead of doing a list reply, I replied directly to Taylor Singletary with full request and response for a failure case and the saved response token/secret from session data. -Marc On Fri, Aug 27, 2010 at 5:16 PM, Marc Mims marc.m...@gmail.com wrote: * Taylor Singletary taylorsinglet...@twitter.com [100827 11:11]: Can you provide any more details about the error response you're giving (like the actual body of the error response)? Taylor, I will capture the full request and response. I assume they are not suitable for posting in a public forum. Should I email the to a...@twitter.com instead? Can you share an example of a signature base string and POST body that failed in this example? Have you verified that the clock on the device/system originating the request is in sync with Twitter's (returned in the Date header of every request) by about 5 minutes? Times are within 1 second. Do you have any successes to compare against? The error seems to occur infrequently. The vast majority of calls succeed on exactly the same code path. The calls are being made with Perl the Net::Twitter library (of which I am the author). Net::Twitter is used by many twitter apps and web apps. Are your HTTP methods in agreement between what your client is actually using (a GET) and the method declared in your signature base string? Yes. -Marc -- 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 -- Matt Harris Developer Advocate, Twitter http://twitter.com/themattharris -- 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 -- 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
[twitter-dev] Re: 401 errors calling access_token
Can you provide any more details about the error response you're giving (like the actual body of the error response)? Can you share an example of a signature base string and POST body that failed in this example? Have you verified that the clock on the device/system originating the request is in sync with Twitter's (returned in the Date header of every request) by about 5 minutes? Do you have any successes to compare against? Are your HTTP methods in agreement between what your client is actually using (a GET) and the method declared in your signature base string? Thanks, Taylor On Aug 26, 3:05 pm, Marc Mims marc.m...@gmail.com wrote: I occasionally see 401 responses calling access_token. At the point of call, I have valid request tokens. The user has been redirected to Twitter, has authorized the app (as evidenced by the fact that the user is redirected to the apps's callback URL). The application uses the oauth_token parameter to retrieve the request token secret from session data. The stored request token and oauth_token parameters match, so I'm confident the correct request token secret is retrieved. Yet, calling access_token with the request token/secret and verifier fails. I thought it was perhaps a spurious error, so I wrote a retry loop. Here's a brief snippet from the application log: access_token returned 401; retrying in 0.25 seconds access_token returned 401; retrying in 0.5 seconds access_token returned 401; retrying in 1 seconds access_token returned 401; retrying in 2 seconds final error = GEThttps://api.twitter.com/oauth/access_token failed: 401 Unauthorized Why would a call to access_token fail immediately after the user has authorized the application? -Marc -- 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
Re: [twitter-dev] Re: 401 errors calling access_token
* Taylor Singletary taylorsinglet...@twitter.com [100827 11:11]: Can you provide any more details about the error response you're giving (like the actual body of the error response)? Taylor, I will capture the full request and response. I assume they are not suitable for posting in a public forum. Should I email the to a...@twitter.com instead? Can you share an example of a signature base string and POST body that failed in this example? Have you verified that the clock on the device/system originating the request is in sync with Twitter's (returned in the Date header of every request) by about 5 minutes? Times are within 1 second. Do you have any successes to compare against? The error seems to occur infrequently. The vast majority of calls succeed on exactly the same code path. The calls are being made with Perl the Net::Twitter library (of which I am the author). Net::Twitter is used by many twitter apps and web apps. Are your HTTP methods in agreement between what your client is actually using (a GET) and the method declared in your signature base string? Yes. -Marc -- 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
