Just to add my two pennies in, I have seen this error quite a bit on my test environment. It normally happened when I sent the user to the oauth page on twitter quite close to the first time I did it - occurs because I was using oAuth as an authentication mechanism.
Kind Regard, Paul Kinlan. 2009/2/19 Matt Sanford <[email protected]> > Hi Rahul, > We were having some trouble with database replication lag last night. > During that time tokens were being created in the master database but were > not available when we went to look them up. When we can't find the token we > return a pretty generic error. I am planning to talk to some people > internally today about how we can make OAuth less fragile in the face of > replication delay. This is what closed beta's are for :). > > Thanks; > — Matt Sanford / @mzsanford > > On Feb 19, 2009, at 03:45 AM, Rahul Waghmare wrote: > > we are getting token as in > > https://twitter.com/oauth/authorize?oauth_token=zb8CGahZPZuDgg3VgUs4fGRgmbHf9aamsSZqmv0P3hk > > but the page shows "403 Forbidden: The server understood the request, but > is refusing to fulfill it." > > why it is happening..... > > Thanks > Rahul > > > >
