The cleanest way to detect the bad/expired token state is to request
/reader/api/0/user-info (which gets you information about the
currently logged-in user). You shouldn't get a 401 in any other case
there (I assume you're referring to 401s you could get when requesting
a shared items stream that you don't have permission to see, as far as
other reasons you could get it).
On Fri, Feb 12, 2010 at 4:59 PM, Nick Bradbury <nick.bradb...@gmail.com> wrote:
> I've changed over to using the auth token in FeedDemon, and my
> understanding is that if the auth token expires, the request will
> return HTTP 401, and the first time HTTP 401 is received the auth
> token should be re-requested. But since HTTP 401 can be received for
> other reasons, I'm wondering how to know for sure that the failure was
> due to a bad/expired token?
> For example, in the case of a bad/expired T token (used with GRAPI
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.