Re: [OAUTH-WG] Returning HTTP 200 on Error for JSONP
<Axel.Nennker@telekom.de> Fri, 20 August 2010 11:19 UTC
Return-Path: <Axel.Nennker@telekom.de>
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 CAF333A69D6 for <oauth@core3.amsl.com>; Fri, 20 Aug 2010 04:19:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level:
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
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 tTpCGGN7JKq3 for <oauth@core3.amsl.com>; Fri, 20 Aug 2010 04:19:25 -0700 (PDT)
Received: from tcmail53.telekom.de (tcmail53.telekom.de [217.5.214.110]) by core3.amsl.com (Postfix) with ESMTP id 63E413A6A7B for <oauth@ietf.org>; Fri, 20 Aug 2010 04:19:25 -0700 (PDT)
Received: from s4de9jsaanm.mgb.telekom.de (HELO S4DE9JSAANM.ost.t-com.de) ([10.125.177.122]) by tcmail51.telekom.de with ESMTP; 20 Aug 2010 13:19:55 +0200
Received: from S4DE9JSAAID.ost.t-com.de ([10.125.177.169]) by S4DE9JSAANM.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.4675); Fri, 20 Aug 2010 13:19:55 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 20 Aug 2010 13:19:53 +0200
Message-ID: <98B37F7D0484184B9DBDCC44B6C8EDA304FB3A95@S4DE9JSAAID.ost.t-com.de>
In-Reply-To: <AANLkTimpvsA=fe8orCwxKN9hOF7P6OvsYbB4VYhUnrhC@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [OAUTH-WG] Returning HTTP 200 on Error for JSONP
Thread-Index: Acs+8ROc/WRWeeTCQHueXI1suzOgQABaGM9g
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><AANLkTikRQdRMwA0HQTrZHpt+tqwVM_MoUNyDWS83i-rq@mail.gmail.com><DB6A95FD-C218-4B46-90AB-B444BDBC407B@mnot.net><AANLkTikbF6UO8K9CsyM7tw5WkLQNdDiiBCNLSjqGH-r3@mail.gmail.com> <AANLkTimpvsA=fe8orCwxKN9hOF7P6OvsYbB4VYhUnrhC @mail.gm ail.com>
From: Axel.Nennker@telekom.de
To: oauth@ietf.org
X-OriginalArrivalTime: 20 Aug 2010 11:19:55.0759 (UTC) FILETIME=[9E050FF0:01CB4059]
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: Fri, 20 Aug 2010 11:19:26 -0000
- [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