Re: [OAUTH-WG] Returning HTTP 200 on Error for JSONP
Robert Sayre <sayrer@gmail.com> Mon, 23 August 2010 23:27 UTC
Return-Path: <sayrer@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 707D33A6B48 for <oauth@core3.amsl.com>; Mon, 23 Aug 2010 16:27:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.599
X-Spam-Level:
X-Spam-Status: No, score=-8.599 tagged_above=-999 required=5 tests=[AWL=-4.000, BAYES_00=-2.599, GB_I_LETTER=-2]
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 N+LHutuCKlJJ for <oauth@core3.amsl.com>; Mon, 23 Aug 2010 16:27:41 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 0E2123A68CC for <oauth@ietf.org>; Mon, 23 Aug 2010 16:27:35 -0700 (PDT)
Received: by wwe15 with SMTP id 15so683335wwe.13 for <oauth@ietf.org>; Mon, 23 Aug 2010 16:28:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=nfZKH+SV2UGhZ+I7QNkb8Kz+mPhJjNdglljdtDeK0hw=; b=NIjYaV18aEe8gdm5poO0FmOtQuGnjlvJfau4zaKgSXORUGPzloVQISGW2RmLl0xlvH TXMSUk8datFFw+YellIC08WykQ7f3I3bcTbjR2MOp9OAp8lGbIRmfDXPnrZ+knBg1tRe W3F4nLoguTlKBTrO6b5drA0Okck08UEUiolSo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=OkuT3fbwrCnsa6eqoViMisTYG7BIrxH86Qtj0OiTb+/2u9HfZ402Dks8UImNfAzzwx XgpCcP/ssbqaZrMFs+SymhEoNoaFaauRlcUSxec9kdmw3cQ51PXiXxVXaJOjVv7Xw0NA oxQqit1QGa9vjIfYcgmB9m7JbkKV01WcCzQ2c=
MIME-Version: 1.0
Received: by 10.216.17.194 with SMTP id j44mr5181592wej.68.1282606088889; Mon, 23 Aug 2010 16:28:08 -0700 (PDT)
Received: by 10.216.28.143 with HTTP; Mon, 23 Aug 2010 16:28:08 -0700 (PDT)
In-Reply-To: <AANLkTi=vGVVzzaQ8AP+bN=YU6_EXavc_M9Xr-sFLvL76@mail.gmail.com>
References: <1643FCF1-841F-41FF-B8A8-43269320CFA8@facebook.com> <D2742806-9180-4A5B-98D5-BFD68AF74EEA@facebook.com> <AANLkTikvz1FNvHN0W4TYyUn=0Nq_At2c+x793XTdwyLm@mail.gmail.com> <AANLkTinBqMvmKuoUq7Fy7XmJue5VEFYcw7qoca=0cWFs@mail.gmail.com> <4C69B719.3060303@lodderstedt.net> <DFB12E92-0E4D-46C2-8103-C74BAE6F65F9@facebook.com> <4C6A25F7.8060301@lodderstedt.net> <AANLkTinHehcMCsmxJt0hvLbLrLC5ERrjG38GDxaAMsiZ@mail.gmail.com> <241FE353-C52A-4505-8620-DEE9CF9F940E@lodderstedt.net> <FC1E2149-F8FF-4010-AAB8-273F8E2DC498@facebook.com> <AANLkTinz4r3AwTva1fu0okobC70Ht1gZei5wjN2eQW3H@mail.gmail.com> <AANLkTinSCrXs1LaLY1ByNFi_Ec9WOr2ETQdpRXYfm+ra@mail.gmail.com> <AANLkTinriRSq9_z4M-Brr59pyhJQm8aGaMnh6dsmmjqH@mail.gmail.com> <AANLkTi=vGVVzzaQ8AP+bN=YU6_EXavc_M9Xr-sFLvL76@mail.gmail.com>
Date: Mon, 23 Aug 2010 19:28:08 -0400
Message-ID: <AANLkTim_xZMDk6LD5W-hxod7BCDO+RPX=kcCumMWukzi@mail.gmail.com>
From: Robert Sayre <sayrer@gmail.com>
To: OAuth WG <oauth@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Subject: Re: [OAUTH-WG] Returning HTTP 200 on Error for JSONP
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: Mon, 23 Aug 2010 23:27:42 -0000
On Tue, Aug 17, 2010 at 10:33 PM, John Panzer <jpanzer@google.com> wrote: > Is there any legit reason other than jsonp specifically? The JSONP response doesn't add any value, so it isn't a legitimate reason anyway. -- Robert Sayre "I would have written a shorter letter, but I did not have the time."
- [OAUTH-WG] Returning HTTP 200 on Error for JSONP Paul Tarjan
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… Luke Shepard
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… Aaron Parecki
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… John Panzer
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… Torsten Lodderstedt
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… Paul Tarjan
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… Torsten Lodderstedt
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… John Panzer
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… Torsten Lodderstedt
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… Luke Shepard
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… John Panzer
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… David Recordon
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… John Panzer
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… Brian Eaton
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… John Panzer
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… Mark Nottingham
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… Brian Eaton
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… Mark Nottingham
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… Eran Hammer-Lahav
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… Luke Shepard
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… Eran Hammer-Lahav
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… Brian Eaton
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… John Panzer
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… Mark Nottingham
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… Mark Nottingham
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… Axel.Nennker
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… George Fletcher
- Re: [OAUTH-WG] Returning HTTP 200 on Error for JS… Robert Sayre