IETF Logo Mail Archive

Re: [OAUTH-WG] Comments on draft-ietf-oauth-v2-03.txt

Evan Gilbert <uidude@google.com> Tue, 11 May 2010 00:43 UTC

Return-Path: <uidude@google.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 8E9C028C0F9 for <oauth@core3.amsl.com>; Mon, 10 May 2010 17:43:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.734
X-Spam-Level:
X-Spam-Status: No, score=-101.734 tagged_above=-999 required=5 tests=[AWL=0.242, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 TBwJec4GhOIB for <oauth@core3.amsl.com>; Mon, 10 May 2010 17:43:55 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id 744573A67AD for <oauth@ietf.org>; Mon, 10 May 2010 17:43:55 -0700 (PDT)
Received: from hpaq12.eem.corp.google.com (hpaq12.eem.corp.google.com [172.25.149.12]) by smtp-out.google.com with ESMTP id o4B0hhtF025957 for <oauth@ietf.org>; Mon, 10 May 2010 17:43:43 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1273538623; bh=t9H+9F5NZ+MfgOseUIBXsSfvdGU=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=mZCqZy4KSUbIggll4Qk8sT/fprhZD3p9wALvJYFCMq2tqqmViN+s9zfBiIMGUgWwy rOV25LQJy1KsFBlqWgppA==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:from:date:message-id: subject:to:cc:content-type:x-system-of-record; b=lO/eVmL2KLfUYiAi06ZKipKcK2u5zFU8NwDCobHv7ZPaRu6sj2kh5/+RDDiSVLg1O XGn7JvOV6a6BbzpYCrQDw==
Received: from qyk35 (qyk35.prod.google.com [10.241.83.163]) by hpaq12.eem.corp.google.com with ESMTP id o4B0hfD9022434 for <oauth@ietf.org>; Mon, 10 May 2010 17:43:42 -0700
Received: by qyk35 with SMTP id 35so6749062qyk.15 for <oauth@ietf.org>; Mon, 10 May 2010 17:43:41 -0700 (PDT)
Received: by 10.229.188.72 with SMTP id cz8mr4132131qcb.75.1273538621282; Mon, 10 May 2010 17:43:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.7.136 with HTTP; Mon, 10 May 2010 17:43:21 -0700 (PDT)
In-Reply-To: <38BB2577-B607-4033-A1C0-F8780DF47746@lodderstedt.net>
References: <4BE730CC.1090607@lodderstedt.net> <AANLkTinnS1STjPtuubuS3_H2AGw1kyruDaFMSeSfE5hN@mail.gmail.com> <38BB2577-B607-4033-A1C0-F8780DF47746@lodderstedt.net>
From: Evan Gilbert <uidude@google.com>
Date: Mon, 10 May 2010 17:43:21 -0700
Message-ID: <AANLkTikoI1Z248reOy_hLwGX1IIXZomJ4qFNFPkL6iRw@mail.gmail.com>
To: Torsten Lodderstedt <torsten@lodderstedt.net>
Content-Type: multipart/alternative; boundary="0016364ecce8211b8f048646d15f"
X-System-Of-Record: true
Cc: "OAuth WG (oauth@ietf.org)" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Comments on draft-ietf-oauth-v2-03.txt
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: Tue, 11 May 2010 00:43:56 -0000

On Mon, May 10, 2010 at 1:20 PM, Torsten Lodderstedt <
torsten@lodderstedt.net> wrote:

>
>
> Am 10.05.2010 um 22:07 schrieb Marius Scurtescu <mscurtescu@google.com>:
>
>
>  On Sun, May 9, 2010 at 3:01 PM, Torsten Lodderstedt
>> <torsten@lodderstedt.net> wrote:
>>
>>> 3.5.1.1.  End-user Grants Authorization
>>>
>>> I would suggest to use JSON encoding here, since the URI fragment is
>>> handled
>>> by a client more or less like a response result.
>>>
>>
>> Evan mentioned that returning JSON in this case is a bad idea because
>> it is very hard to safely parse JSON in JavaScript.
>>
>> Marius
>>
>
> Native JSON support makes it easier.


Only for newer browsers - every web site that wants to work on older browser
would need a JSON parsing library.

Think that people on the form encoding or JSON thread were in rough
agreement that redirect_uri responses should be form encoded.


> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>

v2.23.0 | Report a Bug | By Email