IETF Logo Mail Archive

Re: [OAUTH-WG] application/x-www-form-urlencoded vs JSON

Dick Hardt <dick.hardt@gmail.com> Sat, 01 May 2010 01:51 UTC

Return-Path: <dick.hardt@gmail.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 2BEA83A6851 for <oauth@core3.amsl.com>; Fri, 30 Apr 2010 18:51:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.454
X-Spam-Level:
X-Spam-Status: No, score=-2.454 tagged_above=-999 required=5 tests=[AWL=0.145, 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 38Ak+yLZyTJZ for <oauth@core3.amsl.com>; Fri, 30 Apr 2010 18:51:19 -0700 (PDT)
Received: from mail-pz0-f182.google.com (mail-pz0-f182.google.com [209.85.222.182]) by core3.amsl.com (Postfix) with ESMTP id 708D93A680D for <oauth@ietf.org>; Fri, 30 Apr 2010 18:51:19 -0700 (PDT)
Received: by pzk12 with SMTP id 12so522246pzk.32 for <oauth@ietf.org>; Fri, 30 Apr 2010 18:51:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=p7Cy/v6QEzVSyxgXkwa0uM7eV+KX2wcMm8eC4LtzexY=; b=CPkhW4rX11EMSvjAG0pl3B4uGUb5/MIbsmY8F0jwwfBTw3k1f6NODfuCVOWInNU7mM Ab8BGLhkHi/7JSQdZPRnbX6sxp0ukJcIBsjwSm2ILmwsJwDyoRtq/HiXTtgTGlVEMv30 D4vmpk4Py2WYFvJAU5++XpZI3zzj4uEoH5UE0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=snitx50OjA6vJaGlDxejKS9WIHf2qu+muDzUdxifCSZyk1RVtRZAezufKAh1OYTba5 h1qT/B8XvYxPx17ucFXnw0/Q+8UHGVdveCCfRSthCw9TVCnyP6weQnt/Xn42EX0rjGx5 ZaU/2ZVlhd7zzWksAVAnwmsGv+yfU5NDMAWBo=
Received: by 10.142.250.1 with SMTP id x1mr7233578wfh.109.1272678663348; Fri, 30 Apr 2010 18:51:03 -0700 (PDT)
Received: from [10.0.1.8] (c-67-180-195-167.hsd1.ca.comcast.net [67.180.195.167]) by mx.google.com with ESMTPS id 21sm2415028pzk.4.2010.04.30.18.51.02 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 30 Apr 2010 18:51:02 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset="us-ascii"
From: Dick Hardt <dick.hardt@gmail.com>
In-Reply-To: <9FB1C9A1-6E27-45B8-AFD5-649AD8591AFF@hueniverse.com>
Date: Fri, 30 Apr 2010 18:51:02 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <9DA60271-34A3-4C2F-9299-9AB851F68D2B@gmail.com>
References: <9890332F-E759-4E63-96FE-DB3071194D84@gmail.com> <90C41DD21FB7C64BB94121FBBC2E723438E30A379B@P3PW5EX1MB01.EX1.SECURESERVER.NET> <20100419134825.134951nuzvi35hk4@webmail.df.eu> <90C41DD21FB7C64BB94121FBBC2E723438E5C7F45E@P3PW5EX1MB01.EX1.SECURESERVER.NET> <t2wc334d54e1004200924ja0e7786u9b349a1931098f2a@mail.gmail.com> <l2ofd6741651004201245gdfc6e2a3j10a6e8a3e59f2072@mail.gmail.com> <1271793363.20679.6.camel@Dynamo> <j2wc334d54e1004201417s1bbcc025r76fdb607295f384c@mail.gmail.com> <9FB1C9A1-6E27-45B8-AFD5-649AD8591AFF@hueniverse.com>
To: Eran Hammer-Lahav <eran@hueniverse.com>
X-Mailer: Apple Mail (2.1078)
Cc: "jsmarr@stanfordalumni.org" <jsmarr@stanfordalumni.org>, OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] application/x-www-form-urlencoded vs JSON
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: Sat, 01 May 2010 01:51:20 -0000

On 2010-04-20, at 2:31 PM, Eran Hammer-Lahav wrote:

> All the issues around encoding in 1.0 were about signatures. This is no longer an issue. 

Don't we still support signatures? I still see if in the spec. :)

-- Dick

v2.23.0 | Report a Bug | By Email