Can you share some examples of your requests? I know it's difficult when we're dealing in logins and passwords, but if you obfuscate your consumer secret and login/password and provide an example of both a functional and non-functional request, we'll be able to help you best.
By example I mean: The signature base string generated before creating the signature, the HTTP request you are sending including headers, exact request location, POST body, and the response. If you share code, that's good also. Lots of folks here are good at spotting minor problems. Thanks, Taylor On Thu, Oct 7, 2010 at 6:07 AM, andy <andreas-wilkeme...@andreazw.de> wrote: > The credentials are the same. It will only generate a new nonce and > timestamp. > > > > On 5 Okt., 19:05, Taylor Singletary <taylorsinglet...@twitter.com> > wrote: > > It's likely not the nonce that is invalid in this case -- or the > timestamp. > > > > In this case, the error specifically is indicating that it couldn't > validate > > the request. > > > > Does the alternate 401 vs success happen with the exact same credentials, > or > > are you using different credentials? > > > > Taylor > > > > On Mon, Oct 4, 2010 at 11:41 PM, andy <andreas-wilkeme...@andreazw.de > >wrote: > > > > > Hello, > > > > > I´m using xAuth in an ActionScript 3.0 Project. > > > I still have problems that I sometimes get a successful response, and > > > a couple of times a faulty response. > > > If I get a bad response, then I have the HTTP status code 401 with > > > following error message: > > > Failed to validate oauth signature and token > > > > > The values that are different are the oAuth_nonce and oAuth_timestamp. > > > The oAuth_nonce is determined by a random number. This is determined > > > by the uuid of the current date. Subcontent special characters such > > > as: - removed. Such uuid should be unique. I wonder why I for similar > > > calculations of the nonce, etc. sometimes successful and sometimes get > > > a bad response! > > > > > -- > > > 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 > > -- > 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 > -- 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
