Re: [OAUTH-WG] register prefixes as opposed to full parameter names
Michael D Adams <mike@automattic.com> Wed, 07 July 2010 08:10 UTC
Return-Path: <michael.d.adams@gmail.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 C55EE3A6880 for <oauth@core3.amsl.com>; Wed, 7 Jul 2010 01:10:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 UXmsPAVtw5ut for <oauth@core3.amsl.com>; Wed, 7 Jul 2010 01:10:27 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 7B9123A6883 for <oauth@ietf.org>; Wed, 7 Jul 2010 01:10:27 -0700 (PDT)
Received: by iwn38 with SMTP id 38so2007986iwn.31 for <oauth@ietf.org>; Wed, 07 Jul 2010 01:10:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:sender:received :in-reply-to:references:from:date:x-google-sender-auth:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=wqjFpTSUnOmyDAoXGi3OGlAi4uUIYcxx6GuJ0R+24XY=; b=eRBuH0OnbGu1j+WqCx/lw7+j7F8soYJEgvIrRn7sF9/ri9RJ2FPR7Lcx01b1HlAx9A rGDihuy1dEmFzynUeNVH8F1C4uOXtY+INu/Pbt4VuXh1PSGP0b/cfoUwK6vAComt/OsA KiG/+WX6IF8VPsS9NMJIxNWnM3ugitUjA/MsU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=f/RJtf5XR2Dzi+LMXG8suDA5U+bwoNjLWQqYqhAnBZjNTgbyTuFdOOpqMHVhb3oLRL V99mHikI1oc95MTvnA8Ym7FIctqv6LWtu8As3BFBJuch2yL5QP6oCKJMIfEiKv6R9hAr MWcli9r8Pyy1PV4nOjS/nfRHLB31/cdbUrgXE=
Received: by 10.231.178.103 with SMTP id bl39mr5404041ibb.138.1278490230119; Wed, 07 Jul 2010 01:10:30 -0700 (PDT)
MIME-Version: 1.0
Sender: michael.d.adams@gmail.com
Received: by 10.231.179.143 with HTTP; Wed, 7 Jul 2010 01:10:10 -0700 (PDT)
In-Reply-To: <AANLkTinZTSR-ZIe2kZYYLVKDRkr68JEHP7vxtyOroHGa@mail.gmail.com>
References: <1278439815.2445.8.camel@localhost.localdomain> <C858C2B1.36C16%eran@hueniverse.com> <AANLkTimWZugW68Gkg_CCYZL8TUIbtaNEAlQS7cMTTSZV@mail.gmail.com> <AANLkTimsxRHsXggcEsQhgD04YgbdUlrm_rojSi_SLc-X@mail.gmail.com> <AANLkTikDx54ypvWMlZXGlgXsBi3wErcs3-SxO2hYVQYW@mail.gmail.com> <AANLkTinZTSR-ZIe2kZYYLVKDRkr68JEHP7vxtyOroHGa@mail.gmail.com>
From: Michael D Adams <mike@automattic.com>
Date: Wed, 07 Jul 2010 01:10:10 -0700
X-Google-Sender-Auth: gMt-y0w6RRoqBA4TTAnPoY4fzEM
Message-ID: <AANLkTimY78I-0BC94XVSffwe-sS3HKamXzX39pj04JKE@mail.gmail.com>
To: Marius Scurtescu <mscurtescu@google.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] register prefixes as opposed to full parameter names
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, 07 Jul 2010 08:10:28 -0000
On Wed, Jul 7, 2010 at 12:57 AM, Michael D Adams <mike@automattic.com> wrote: > WordPress uses query parameters. A WordPress plugin that enables > OAuth, though, would have to register new URL handlers with WordPress > to act as the token and end-user authorization endpoints. Having done > so, the plugin would then have complete control over how to behave > under any query parameters, entity-body contents, or headers: core, > extension, site specific or otherwise. Actually, for a small minority of WordPress sites wanting to enable OAuth (those not supporting so called "pretty permalinks"), the WordPress plugin would need to internally reserve one query parameter to get the ball rolling. Theoretically, that need leads to the possibility of conflict, but I'm not worried about it. Mike --mdawaffe
- [OAUTH-WG] register prefixes as opposed to full p… Marius Scurtescu
- Re: [OAUTH-WG] register prefixes as opposed to fu… Eran Hammer-Lahav
- Re: [OAUTH-WG] register prefixes as opposed to fu… Marius Scurtescu
- Re: [OAUTH-WG] register prefixes as opposed to fu… Eran Hammer-Lahav
- Re: [OAUTH-WG] register prefixes as opposed to fu… Marius Scurtescu
- Re: [OAUTH-WG] register prefixes as opposed to fu… Eran Hammer-Lahav
- Re: [OAUTH-WG] register prefixes as opposed to fu… Marius Scurtescu
- Re: [OAUTH-WG] register prefixes as opposed to fu… Justin Richer
- Re: [OAUTH-WG] register prefixes as opposed to fu… Eran Hammer-Lahav
- Re: [OAUTH-WG] register prefixes as opposed to fu… William Mills
- Re: [OAUTH-WG] register prefixes as opposed to fu… Marius Scurtescu
- Re: [OAUTH-WG] register prefixes as opposed to fu… Michael D Adams
- Re: [OAUTH-WG] register prefixes as opposed to fu… Marius Scurtescu
- Re: [OAUTH-WG] register prefixes as opposed to fu… Michael D Adams
- Re: [OAUTH-WG] register prefixes as opposed to fu… Michael D Adams
- Re: [OAUTH-WG] register prefixes as opposed to fu… Marius Scurtescu
- Re: [OAUTH-WG] register prefixes as opposed to fu… Michael D Adams