[OAUTH-WG] Rename callback => callback_uri
Naitik Shah <naitik@facebook.com> Sat, 10 April 2010 19:35 UTC
Return-Path: <naitik@facebook.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 DEE7B3A67F0 for <oauth@core3.amsl.com>; Sat, 10 Apr 2010 12:35:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.406
X-Spam-Level:
X-Spam-Status: No, score=-1.406 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, IP_NOT_FRIENDLY=0.334, 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 NjSnjsRUHkyF for <oauth@core3.amsl.com>; Sat, 10 Apr 2010 12:35:59 -0700 (PDT)
Received: from mailout-sf2p.facebook.com (mailout-snc1.facebook.com [69.63.179.25]) by core3.amsl.com (Postfix) with ESMTP id 3E8703A672E for <oauth@ietf.org>; Sat, 10 Apr 2010 12:35:59 -0700 (PDT)
Received: from mail.thefacebook.com ([192.168.18.198]) by pp02.snc1.tfbnw.net (8.14.3/8.14.3) with ESMTP id o3AJZJ7E015868 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <oauth@ietf.org>; Sat, 10 Apr 2010 12:35:19 -0700
Received: from sc-hub06.TheFacebook.com (192.168.18.83) by sc-hub03.TheFacebook.com (192.168.18.198) with Microsoft SMTP Server (TLS) id 14.0.682.1; Sat, 10 Apr 2010 12:35:53 -0700
Received: from SC-MBXC1.TheFacebook.com ([192.168.18.102]) by sc-hub06.TheFacebook.com ([192.168.18.83]) with mapi; Sat, 10 Apr 2010 12:35:52 -0700
From: Naitik Shah <naitik@facebook.com>
To: "oauth@ietf.org" <oauth@ietf.org>
Date: Sat, 10 Apr 2010 12:35:52 -0700
Thread-Topic: Rename callback => callback_uri
Thread-Index: AcrY5QgYzwsqKHvhTbuKpWjgY2XeCg==
Message-ID: <9C30AE64-7DB8-4B6B-879B-61CB71BF74BB@facebook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5, 1.2.40, 4.0.166 definitions=2010-04-10_04:2010-02-06, 2010-04-10, 2010-04-10 signatures=0
X-Mailman-Approved-At: Wed, 14 Apr 2010 10:55:49 -0700
Subject: [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: Sat, 10 Apr 2010 19:36:42 -0000
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-WG] Rename callback => callback_uri Naitik Shah
- Re: [OAUTH-WG] Rename callback => callback_uri Eran Hammer-Lahav
- Re: [OAUTH-WG] Rename callback => callback_uri Luke Shepard
- Re: [OAUTH-WG] Rename callback => callback_uri Marius Scurtescu
- Re: [OAUTH-WG] Rename callback => callback_uri Richard Barnes
- Re: [OAUTH-WG] Rename callback => callback_uri Luke Shepard
- Re: [OAUTH-WG] Rename callback => callback_uri Evan Gilbert
- Re: [OAUTH-WG] Rename callback => callback_uri Richard Barnes
- Re: [OAUTH-WG] Rename callback => callback_uri Evan Gilbert
- Re: [OAUTH-WG] Rename callback => callback_uri Luke Shepard
- Re: [OAUTH-WG] Rename callback => callback_uri Evan Gilbert
- Re: [OAUTH-WG] Rename callback => callback_uri Naitik Shah
- Re: [OAUTH-WG] Rename callback => callback_uri Eran Hammer-Lahav
- Re: [OAUTH-WG] Rename callback => callback_uri Evan Gilbert
- Re: [OAUTH-WG] Rename callback => callback_uri Eran Hammer-Lahav