Re: [OAUTH-WG] section 3.2 error in draft-ietf-oauth-v2-10
Eran Hammer-Lahav <eran@hueniverse.com> Wed, 01 December 2010 06:35 UTC
Return-Path: <eran@hueniverse.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 9ECA03A6CEE for <oauth@core3.amsl.com>; Tue, 30 Nov 2010 22:35:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.501
X-Spam-Level:
X-Spam-Status: No, score=-2.501 tagged_above=-999 required=5 tests=[AWL=0.098, BAYES_00=-2.599]
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 OW+OaTEQIORB for <oauth@core3.amsl.com>; Tue, 30 Nov 2010 22:35:42 -0800 (PST)
Received: from p3plex1out02.prod.phx3.secureserver.net (p3plex1out02.prod.phx3.secureserver.net [72.167.180.18]) by core3.amsl.com (Postfix) with SMTP id A1F1F3A6CF1 for <oauth@ietf.org>; Tue, 30 Nov 2010 22:35:42 -0800 (PST)
Received: (qmail 3692 invoked from network); 1 Dec 2010 06:36:54 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.20) by p3plex1out02.prod.phx3.secureserver.net with SMTP; 1 Dec 2010 06:36:53 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT002.EX1.SECURESERVER.NET ([72.167.180.20]) with mapi; Tue, 30 Nov 2010 23:36:54 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Nick Walker <nick@concentricsky.com>, "oauth@ietf.org" <oauth@ietf.org>
Date: Tue, 30 Nov 2010 23:37:02 -0700
Thread-Topic: [OAUTH-WG] section 3.2 error in draft-ietf-oauth-v2-10
Thread-Index: AcuF6Se/h2A5aCygTxqraMnkZ48tWgLOOV/w
Message-ID: <90C41DD21FB7C64BB94121FBBC2E72343D4B06593D@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <20101116234514.GE31381@concentricsky.com>
In-Reply-To: <20101116234514.GE31381@concentricsky.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [OAUTH-WG] section 3.2 error in draft-ietf-oauth-v2-10
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: Wed, 01 Dec 2010 06:35:49 -0000
4.3 would be the wrong behavior. I think it should just be an informative page to let the end-user know something broke.
New text:
If the request fails due to a missing or invalid redirection URI, the authorization
server SHOULD inform the end-user of the error, and MUST NOT redirect the end-user's
user-agent to the invalid redirection URI.
EHL
> -----Original Message-----
> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf
> Of Nick Walker
> Sent: Tuesday, November 16, 2010 3:45 PM
> To: oauth@ietf.org
> Subject: [OAUTH-WG] section 3.2 error in draft-ietf-oauth-v2-10
>
> In section 3.2 of draft-ietf-oauth-v2-10:
>
> "... if the request is invalid, the authorization server informs
> the client by adding the following parameters to the redirection
> URI query component ..."
>
> This leads to issuing an HTTP 302 response with an invalid Location header if
> the redirect_uri parameter is missing or invalid.
>
> I believe the correct behavior in this case is the same as in section 4.3.
>
> Nick
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
- [OAUTH-WG] section 3.2 error in draft-ietf-oauth-… Nick Walker
- Re: [OAUTH-WG] section 3.2 error in draft-ietf-oa… Eran Hammer-Lahav