[OAUTH-WG] Redirects

"Manger, James H" <James.H.Manger@team.telstra.com> Fri, 07 May 2010 05:30 UTC

Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D1B0A3A6BCE for <oauth@core3.amsl.com>; Thu, 6 May 2010 22:30:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.272
X-Spam-Level: *
X-Spam-Status: No, score=1.272 tagged_above=-999 required=5 tests=[AWL=-0.428, BAYES_50=0.001, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, HTML_MESSAGE=0.001, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cPxUwZ0I9q6t for <oauth@core3.amsl.com>; Thu, 6 May 2010 22:30:30 -0700 (PDT)
Received: from ipxbno.tcif.telstra.com.au (ipxbno.tcif.telstra.com.au [203.35.82.204]) by core3.amsl.com (Postfix) with ESMTP id E09963A6BEE for <oauth@ietf.org>; Thu, 6 May 2010 22:21:59 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.52,346,1270389600"; d="scan'208,217";a="2198271"
Received: from unknown (HELO ipcdni.tcif.telstra.com.au) ([10.97.216.212]) by ipobni.tcif.telstra.com.au with ESMTP; 07 May 2010 15:21:46 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,5974"; a="1679282"
Received: from wsmsg3707.srv.dir.telstra.com ([172.49.40.81]) by ipcdni.tcif.telstra.com.au with ESMTP; 07 May 2010 15:21:46 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by wsmsg3707.srv.dir.telstra.com ([172.49.40.81]) with mapi; Fri, 7 May 2010 15:21:46 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: OAuth WG <oauth@ietf.org>
Date: Fri, 07 May 2010 15:21:45 +1000
Thread-Topic: [OAUTH-WG] Redirects
Thread-Index: AcrtmoBx8bDl1v+GT7af9oQzU2FQBwACIrsg
Message-ID: <255B9BB34FB7D647A506DC292726F6E112631B257D@WSMSG3153V.srv.dir.telstra.com>
References: <255B9BB34FB7D647A506DC292726F6E11263073D6D@WSMSG3153V.srv.dir.telstra.com> <q2hfd6741651005062105y46152452x370fac0dd12d55c6@mail.gmail.com>
In-Reply-To: <q2hfd6741651005062105y46152452x370fac0dd12d55c6@mail.gmail.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-AU
Content-Type: multipart/alternative; boundary="_000_255B9BB34FB7D647A506DC292726F6E112631B257DWSMSG3153Vsrv_"
MIME-Version: 1.0
Subject: [OAUTH-WG] Redirects
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 May 2010 05:30:32 -0000

How should an OAuth client app behave when it gets an HTTP redirect on requesting a protected resource?

Similarly, how should it behave when it follows any other link in a response?



Obviously it should make a new request to the URI in the redirect or link — that is normal HTTP and hypertext behaviour.

The question is does the token get sent with the new request?





I think the spec needs to provide an answer, even if it isn’t my suggestion of an “sites” list when a token is issued.



--

James Manger