I don't have the timestamp of a request that I can get an exact measurement from, but it is < 30 seconds.
Jonathon On May 18, 9:57 am, Taylor Singletary <taylorsinglet...@twitter.com> wrote: > Jonathon, > > When you get that error in the access token step, how much time has passed > since when the request token was issued before attempting to be exchanged > for an access token? > > Taylor Singletary > Developer Advocate, Twitterhttp://twitter.com/episod > > > > On Mon, May 17, 2010 at 6:00 PM, Jonathon Hill <jhill9...@gmail.com> wrote: > > I too am experiencing this issue with OAuth calls. At random times / > > oauth/access_token results in a response similar to the following: > > > Date: Mon, 17 May 2010 21:27:26 GMT > > Server: hi > > Status: 401 Unauthorized > > WWW-Authenticate: Basic realm="Twitter API" > > X-Transaction: 1274131646-92315-8359 > > Last-Modified: Mon, 17 May 2010 21:27:26 GMT > > Content-Type: text/html; charset=utf-8 > > Content-Length: 136 > > Pragma: no-cache > > X-Revision: DEV > > Expires: Tue, 31 Mar 1981 05:00:00 GMT > > Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- > > check=0 > > Set-Cookie: > > _twitter_sess=BAh7CToPY3JlYXRlZF9hdGwrCFEJKqgoAToHaWQiJTE5Y2ZhYjRmZDAzNDhi > > %250AYzQ4OGIwZDI1YjVmZDlkNWQ5IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy > > > %250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsAOhF0cmFuc19wcm9tcHQw--3f410249b56aa9a5ce6c444e7f36dfe6fb446a58; > > domain=.twitter.com; path=/ > > Vary: Accept-Encoding > > Connection: close > > > <?xml version="1.0" encoding="UTF-8"?> > > <hash> > > <request>/oauth/access_token</request> > > <error>Invalid / expired Token</error> > > </hash> > > > Jonathon Hill > > @compwright > > @rainmakerapp > > > On May 11, 10:15 am, Dewald Pretorius <dpr...@gmail.com> wrote: > > > In fact, the API seems to be really borked at the moment. > > > > I've been running more tests on friends_timeline.json, and the > > > following happens: > > > > 1) Sometimes the connection is refused. > > > 2) Sometimes I get a 200 OK with an empty JSON array, and seconds > > > later with the very next call on the same Twitter account I get a 200 > > > OK with a fully populated JSON array. > > > 3) On some accounts I get "401Invalid / expired token", where the > > > token on my side has not changed and the connection is present in the > > > Twitter account's Connections tab.
