X-BeenThere: fougrapi@googlegroups.com
Received: by 10.101.182.11 with SMTP id j11ls392265anp.0.p; Fri, 12 Feb 2010 
	14:05:18 -0800 (PST)
Received: by 10.101.135.17 with SMTP id m17mr1806636ann.27.1266012318136;
        Fri, 12 Feb 2010 14:05:18 -0800 (PST)
Received: by 10.101.135.17 with SMTP id m17mr1806635ann.27.1266012318108;
        Fri, 12 Feb 2010 14:05:18 -0800 (PST)
Return-Path: <mih...@google.com>
Received: from smtp-out.google.com (wpay13.hot.corp.google.com [172.24.198.13])
        by gmr-mx.google.com with ESMTP id 19si111250ywh.14.2010.02.12.14.05.17;
        Fri, 12 Feb 2010 14:05:17 -0800 (PST)
Received-SPF: pass (google.com: domain of mih...@google.com designates 172.24.198.13 as permitted sender)
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of mih...@google.com designates 172.24.198.13 as permitted sender) smtp.mail=mih...@google.com; dkim=pass (test mode) header...@google.com
Received: from wpaz13.hot.corp.google.com (wpaz13.hot.corp.google.com [172.24.198.77])
	by smtp-out.google.com with ESMTP id o1CM5GFp008588
	for <fougrapi@googlegroups.com>; Fri, 12 Feb 2010 14:05:17 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta;
	t=1266012317; bh=ELOalIgFFdB/lXqa7e6TZfI2ojU=;
	h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From:
	 To:Content-Type:Content-Transfer-Encoding;
	b=QQzxq6Ncb/ZfOfSu8Dj9qVkDmVil1TpMNytMeAkb6ryXHq9m9qz5w78YUOklpYkU/
	 1LB+HCpewBu/D5B1bW+VQ==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to:
	content-type:content-transfer-encoding:x-system-of-record;
	b=Mx+/w/pQTqXDgNql/5Si+Em5wxg89wBF633+XCRTrhTqP8JMwGHkki6f1vPAkfX4D
	TWsGJMCd1rWZ/mttIJpHg==
Received: from qyk5 (qyk5.prod.google.com [10.241.83.133])
	by wpaz13.hot.corp.google.com with ESMTP id o1CM4sKY019058
	for <fougrapi@googlegroups.com>; Fri, 12 Feb 2010 14:05:16 -0800
Received: by qyk5 with SMTP id 5so1832753qyk.17
        for <fougrapi@googlegroups.com>; Fri, 12 Feb 2010 14:05:16 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.212.83 with SMTP id gr19mr827376qcb.30.1266012315819; Fri, 
	12 Feb 2010 14:05:15 -0800 (PST)
In-Reply-To: <72987520-5fdd-47b0-ba7d-8ed4b18ba...@o3g2000yqb.googlegroups.com>
References: <995a6740-770f-4c17-8a06-3cd25a099...@b36g2000pri.googlegroups.com>
	 <c8c2cbfa-f539-4f13-b807-85a42ce77...@m16g2000yqc.googlegroups.com>
	 <b3bff971-ad92-44d7-8e4a-5ca886bad...@k19g2000yqc.googlegroups.com>
	 <264cf901002110801t2f94c1fet17ffc6fad7ac0...@mail.gmail.com>
	 <5575e52a-55d8-45f4-b1fc-6dffdcebe...@a5g2000yqi.googlegroups.com>
	 <72987520-5fdd-47b0-ba7d-8ed4b18ba...@o3g2000yqb.googlegroups.com>
Date: Fri, 12 Feb 2010 17:05:15 -0500
Message-ID: <264cf901002121405r3b5555cfqaedc3c78e3bdc...@mail.gmail.com>
Subject: Re: Changes to sending authenticated requests to Google Reader
From: Mihai Parparita <mih...@google.com>
To: fougrapi@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true

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).

Mihai

On Fri, Feb 12, 2010 at 4:59 PM, Nick Bradbury <nick.bradb...@gmail.com> wr=
ote:
> 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. =A0But 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
> calls), the request will return HTTP 400, and the HTTP headers will
> include "X-Reader-Google-Bad-Token: true." =A0Is there anything similar
> for a bad/expired auth token?
>