Re: [OAUTH-WG] Rename callback => callback_uri

Marius Scurtescu <mscurtescu@google.com> Thu, 15 April 2010 22:16 UTC

Return-Path: <mscurtescu@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 0FA6C3A6AA0 for <oauth@core3.amsl.com>; Thu, 15 Apr 2010 15:16:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.579
X-Spam-Level:
X-Spam-Status: No, score=-101.579 tagged_above=-999 required=5 tests=[AWL=0.398, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 GOYOKoNcPx+b for <oauth@core3.amsl.com>; Thu, 15 Apr 2010 15:16:47 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id EC17F3A6A91 for <oauth@ietf.org>; Thu, 15 Apr 2010 15:16:24 -0700 (PDT)
Received: from hpaq1.eem.corp.google.com (hpaq1.eem.corp.google.com [10.3.21.1]) by smtp-out.google.com with ESMTP id o3FMGEks031598 for <oauth@ietf.org>; Fri, 16 Apr 2010 00:16:16 +0200
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1271369776; bh=GdcdZkizoHwMEGscud1IGaQdmgQ=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type:Content-Transfer-Encoding; b=T65q8KuZjAX984qSIeXrBUeZeIMG+gpjiubrc2BwE06r2afi1BchqlmLu6e6eVPTg Shmc12r7eNMs8uud2lpnQ==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:from:date:message-id: subject:to:cc:content-type:content-transfer-encoding:x-system-of-record; b=wl3FmaPJdh9PL5Wz7wIRqEItrcogT0hc9BFIwUDQOCDksYGJJ1OjgzAupBP2Hxh1Y fXBlHj3QbS6WOnhoZ4jRQ==
Received: from pvg16 (pvg16.prod.google.com [10.241.210.144]) by hpaq1.eem.corp.google.com with ESMTP id o3FMGDZ2022073 for <oauth@ietf.org>; Fri, 16 Apr 2010 00:16:13 +0200
Received: by pvg16 with SMTP id 16so1153022pvg.40 for <oauth@ietf.org>; Thu, 15 Apr 2010 15:16:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.141.107.2 with HTTP; Thu, 15 Apr 2010 15:15:52 -0700 (PDT)
In-Reply-To: <2513A610118CC14C8E622C376C8DEC93D54D66DCA7@SC-MBXC1.TheFacebook.com>
References: <9C30AE64-7DB8-4B6B-879B-61CB71BF74BB@facebook.com> <C7EC567E.322EE%eran@hueniverse.com> <2513A610118CC14C8E622C376C8DEC93D54D66DCA7@SC-MBXC1.TheFacebook.com>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Thu, 15 Apr 2010 15:15:52 -0700
Received: by 10.141.1.1 with SMTP id d1mr1187127rvi.89.1271369772115; Thu, 15 Apr 2010 15:16:12 -0700 (PDT)
Message-ID: <i2t74caaad21004151515o29576c42tc468c8a86585535a@mail.gmail.com>
To: Luke Shepard <lshepard@facebook.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
Cc: Naitik Shah <naitik@facebook.com>, OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Rename callback => callback_uri
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, 15 Apr 2010 22:16:48 -0000

How about oauth_callback?

Marius



On Thu, Apr 15, 2010 at 2:41 PM, Luke Shepard <lshepard@facebook.com> wrote:
> We already had one developer try it out and get confused because the server
> tried to treat the callback URL as a JSONP callback.
>
>
>
> The protected resource typically accepts “callback” as a parameter to
> support JSONP. If a developer accidentally passes in callback there (maybe
> they got confused) then the server can’t give a normal error message –
> instead it needs to either detect that it looks like a URL or otherwise
> reject it.
>
>
>
> On a related note, I think it’s more confusing calling it something
> different in the user-agent flow (redirector) when it’s essentially doing
> the same thing.
>
>
>
>
>
> From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf Of
> Eran Hammer-Lahav
> Sent: Thursday, April 15, 2010 5:37 AM
> To: Naitik Shah; OAuth WG
> Subject: Re: [OAUTH-WG] Rename callback => callback_uri
>
>
>
> I don’t think it is that confusing. Its a completely different context from
> where JSON-P is used (note that in the User-Agent flow it is called
> something else).
>
> EHL
>
>
> On 4/10/10 12:35 PM, "Naitik Shah" <naitik@facebook.com> wrote:
>
> With the simplified params, the callback url parameter is now just
> "callback". Since most major API providers already use "callback" to signify
> JSON-P callback, can we rename this to "callback_uri"? This will help avoid
> collisions and confusion.
>
>
> -Naitik
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
>