X-BeenThere: fougrapi@googlegroups.com
Received: by 10.101.183.7 with SMTP id k7ls231312anp.1.p; Thu, 11 Feb 2010 
	07:59:00 -0800 (PST)
Received: by 10.101.136.35 with SMTP id o35mr65160ann.0.1265903940184;
        Thu, 11 Feb 2010 07:59:00 -0800 (PST)
Received: by 10.101.136.35 with SMTP id o35mr65158ann.0.1265903940152;
        Thu, 11 Feb 2010 07:59:00 -0800 (PST)
Return-Path: <skyntc...@gmail.com>
Received: from mail-yw0-f160.google.com (mail-yw0-f160.google.com [209.85.211.160])
        by gmr-mx.google.com with ESMTP id 18si277685yxe.0.2010.02.11.07.59.00;
        Thu, 11 Feb 2010 07:59:00 -0800 (PST)
Received-SPF: pass (google.com: domain of skyntc...@gmail.com designates 209.85.211.160 as permitted sender) client-ip=209.85.211.160;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of skyntc...@gmail.com designates 209.85.211.160 as permitted sender) smtp.mail=skyntc...@gmail.com
Received: by ywh32 with SMTP id 32so3058095ywh.10
        for <fougrapi@googlegroups.com>; Thu, 11 Feb 2010 07:59:00 -0800 (PST)
MIME-Version: 1.0
Received: by 10.100.228.1 with SMTP id a1mr7928anh.16.1265903940083; Thu, 11 
	Feb 2010 07:59:00 -0800 (PST)
Date: Thu, 11 Feb 2010 07:59:00 -0800 (PST)
In-Reply-To: <fff965d6-307b-4f7d-9e4f-de849424bf7b@x22g2000yqx.googlegroups.com>
X-IP: 74.219.229.210
References: <995a6740-770f-4c17-8a06-3cd25a099a62@b36g2000pri.googlegroups.com> 
	<c8c2cbfa-f539-4f13-b807-85a42ce77a6f@m16g2000yqc.googlegroups.com> 
	<fff965d6-307b-4f7d-9e4f-de849424bf7b@x22g2000yqx.googlegroups.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; 
	rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7,gzip(gfe),gzip(gfe)
Message-ID: <24c1ddb7-abf8-4b86-8c30-07d37dca7804@a5g2000yqi.googlegroups.com>
Subject: Re: Changes to sending authenticated requests to Google Reader
From: Stefan Kyntchev <skyntc...@gmail.com>
To: Friends of the Unofficial Google Reader API <fougrapi@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I also did a test with the new method this morning and it appears to
work correctly (only Auth header and no SID cookie).
As I am about to push a new public release of BeyondPod, is is safe to
use only the new "Auth header",  method or should I use both the
header and SID for the time being?

Stefan

On Feb 11, 10:29=A0am, Nick Bradbury <nick.bradb...@gmail.com> wrote:
> > 1.) Will there be an overlap where both the SID cookie and the
> > new header will work for authorization?
>
> My tests with FeedDemon show that both of these work right now - you
> can authenticate using either the SID cookie or the auth token.