Re: [OAUTH-WG] Returning HTTP 200 on Error for JSONP
Mark Nottingham <mnot@mnot.net> Thu, 19 August 2010 23:00 UTC
Return-Path: <mnot@mnot.net>
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 09CD63A691A for <oauth@core3.amsl.com>; Thu, 19 Aug 2010 16:00:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.908
X-Spam-Level:
X-Spam-Status: No, score=-104.908 tagged_above=-999 required=5 tests=[AWL=-2.309, BAYES_00=-2.599, 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 xQfxO4kdd+ws for <oauth@core3.amsl.com>; Thu, 19 Aug 2010 16:00:28 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by core3.amsl.com (Postfix) with ESMTP id D9D6D3A6899 for <oauth@ietf.org>; Thu, 19 Aug 2010 16:00:27 -0700 (PDT)
Received: from chancetrain-lm.mnot.net (unknown [118.209.102.210]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 3A3DA509DA; Thu, 19 Aug 2010 19:00:55 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <B2D9DA6A-8949-4D2F-9E7C-EB7DF2D8AB2B@mnot.net>
Date: Fri, 20 Aug 2010 09:00:55 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <CA8D6B96-6267-42FF-8833-7E4F428F9831@mnot.net>
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> <B2D9DA6A-8949-4D2F-9E7C-EB7DF 2D8AB2B@mnot.net>
To: OAuth WG <oauth@ietf.org>
X-Mailer: Apple Mail (2.1081)
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: Thu, 19 Aug 2010 23:00:29 -0000
How fortuitous: http://blogs.msdn.com/b/ieinternals/archive/2010/08/19/http-error-pages-in-internet-explorer.aspx On 19/08/2010, at 8:47 AM, Mark Nottingham wrote: > See: > http://support.microsoft.com/kb/294807 > > > On 19/08/2010, at 1:55 AM, Brian Eaton wrote: > >> On Tue, Aug 17, 2010 at 11:36 PM, Mark Nottingham <mnot@mnot.net> wrote: >>>> The other reason people get funny with these status codes has to do >>>> with browser behavior. Sometimes browsers react in funny ways to >>>> funny HTTP status codes. To be on the safe side, developers tend to >>>> return an HTTP 200 with whatever they want the user to see. >>> >>> Can you give concrete examples, please? What browsers do what exactly, under what circumstances? >> >> Here's a well-known example: >> http://malektips.com/internet-explorer-8-disable-friendly-error-messages.html. >> >> Fuzzier stuff is in handling of things like WWW-Authenticate headers >> on HTTP 200 responses, or 401s with unknown authorization challenges. > > > -- > Mark Nottingham http://www.mnot.net/ > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth -- Mark Nottingham http://www.mnot.net/
- [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