Tokens should never expire.  However, you can only make that request once.
 If you try to make it again with the same request request token, then you
will get the "expired token" error.

On Wed, Oct 14, 2009 at 12:02 AM, BlueSkies <scarter28m-goo...@yahoo.com>wrote:

>
>
> When my application requests an OAuth token on behalf of a user trying
> to login, I have been seeing some errors:
>
> Frequently: "/oauth/access_token Invalid / expired Token"
>
> What is the length of time that a token is supposed to be valid for?
> Is this documented and can it be extended?  I'm sure that I probably
> lose quite a few first time users when this happens.  I imagine that
> they probably bring up my login page, get distracted and then run into
> this problem when they eventually try to log in.
>
>
> Occasionally: "Twitter is over capacity."
>
> Would it make any sense to prioritize token handling when Twitter is
> at capacity?  This is also an issue with wanting to allow my new users
> to login easily, even if they can't tweet right away (to avoid user
> conversion loss).  My existing users probably never experience this
> issue with tokens when Twitter is at capacity, since my application
> caches credentials (as most other apps are probably also doing), so
> they don't normally go through my OAuth login flow very often.
>
>
> Not often: "Unknown SSL protocol error in connection to twitter.com:
> 443"
>
> I'm not sure what causes this?  I don't see it too often.
>
>
> - Scott
>
>
>
>

Reply via email to