IETF Logo Mail Archive

Re: [OAUTH-WG] Returning HTTP 200 on Error for JSONP

John Panzer <jpanzer@google.com> Wed, 18 August 2010 16:18 UTC

Return-Path: <jpanzer@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 2F7473A67F9 for <oauth@core3.amsl.com>; Wed, 18 Aug 2010 09:18:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.91
X-Spam-Level:
X-Spam-Status: No, score=-105.91 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, 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 L4x1Ww4yHRzQ for <oauth@core3.amsl.com>; Wed, 18 Aug 2010 09:18:04 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id CD7BB3A65A6 for <oauth@ietf.org>; Wed, 18 Aug 2010 09:18:03 -0700 (PDT)
Received: from wpaz37.hot.corp.google.com (wpaz37.hot.corp.google.com [172.24.198.101]) by smtp-out.google.com with ESMTP id o7IGIcL8013999 for <oauth@ietf.org>; Wed, 18 Aug 2010 09:18:38 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1282148318; bh=cwgF7beVyw3eivvhSm2914k96JM=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type:Content-Transfer-Encoding; b=HDsID6SRB5soi87x3G3FmJzSEIapgt/O5Y9QNtg+wN2BvhFtkZjswDSuRLdWEy81m Cxhkv1Mj/qT0VFXtjYN0A==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:content-transfer-encoding:x-system-of-record; b=GLzwOmthVwIXfmBOL+iYBWmlyO5aZVyEUBQT5NRUsiKhQplXXl1E+nrS/mUN8NNT7 JntkeeIJyeVBBPaqDWMcw==
Received: from gwb19 (gwb19.prod.google.com [10.200.2.19]) by wpaz37.hot.corp.google.com with ESMTP id o7IGIbYO011079 for <oauth@ietf.org>; Wed, 18 Aug 2010 09:18:37 -0700
Received: by gwb19 with SMTP id 19so351819gwb.29 for <oauth@ietf.org>; Wed, 18 Aug 2010 09:18:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.101.87.12 with SMTP id p12mr9607236anl.73.1282148317311; Wed, 18 Aug 2010 09:18:37 -0700 (PDT)
Received: by 10.101.126.6 with HTTP; Wed, 18 Aug 2010 09:18:37 -0700 (PDT)
In-Reply-To: <AANLkTikbF6UO8K9CsyM7tw5WkLQNdDiiBCNLSjqGH-r3@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> <AANLkTikRQdRMwA0HQTrZHpt+tqwVM_MoUNyDWS83i-rq@mail.gmail.com> <DB6A95FD-C218-4B46-90AB-B444BDBC407B@mnot.net> <AANLkTikbF6UO8K9CsyM7tw5WkLQNdDiiBCNLSjqGH-r3@mail.gmail.com>
Date: Wed, 18 Aug 2010 09:18:37 -0700
Message-ID: <AANLkTimpvsA=fe8orCwxKN9hOF7P6OvsYbB4VYhUnrhC@mail.gmail.com>
From: John Panzer <jpanzer@google.com>
To: Brian Eaton <beaton@google.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
Cc: OAuth WG <oauth@ietf.org>
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: Wed, 18 Aug 2010 16:18:05 -0000

For ie silliness, sop is to include a lot of text in the 5xx so it'll
show your message instead of its own.

I've done lots of www-authenticate with 200's, always heard worries
from web engineers, never had a bug report.  Ymmv.

On Wednesday, August 18, 2010, Brian Eaton <beaton@google.com> 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.
>

-- 
--
John Panzer / Google
jpanzer@google.com / abstractioneer.org / @jpanzer

v2.30.2 | Report a Bug | By Email | System Status