IETF Logo Mail Archive

Re: [OAUTH-WG] register prefixes as opposed to full parameter names

Marius Scurtescu <mscurtescu@google.com> Wed, 07 July 2010 17:36 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 117EB3A68C0 for <oauth@core3.amsl.com>; Wed, 7 Jul 2010 10:36:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.977
X-Spam-Level:
X-Spam-Status: No, score=-101.977 tagged_above=-999 required=5 tests=[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 FislEXalsKpQ for <oauth@core3.amsl.com>; Wed, 7 Jul 2010 10:36:01 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id BCDCF3A68BC for <oauth@ietf.org>; Wed, 7 Jul 2010 10:31:41 -0700 (PDT)
Received: from hpaq11.eem.corp.google.com (hpaq11.eem.corp.google.com [172.25.149.11]) by smtp-out.google.com with ESMTP id o67HVW3I026485 for <oauth@ietf.org>; Wed, 7 Jul 2010 10:31:32 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1278523893; bh=zxGrk37LMMqr/Y2I5b22teGdJDM=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type:Content-Transfer-Encoding; b=AT+XgRw6fiW50I0Aohp/I1fQbLSdzTossXKAgfNRpg3z8pPkradyaGVxK0OmToicI MfzcsngyVWCJPPSJYlgrw==
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=h4UKcjSQbIZTpNw0feRnLZJqGMTZrhXY+AnAsQlPNWC4uWtfWdybl/skAhIYHWVED BImgA9xXPP3ZrHe//Qayg==
Received: from gwj17 (gwj17.prod.google.com [10.200.10.17]) by hpaq11.eem.corp.google.com with ESMTP id o67HVVuX021388 for <oauth@ietf.org>; Wed, 7 Jul 2010 10:31:31 -0700
Received: by gwj17 with SMTP id 17so4167682gwj.23 for <oauth@ietf.org>; Wed, 07 Jul 2010 10:31:31 -0700 (PDT)
Received: by 10.100.194.10 with SMTP id r10mr8447415anf.225.1278523891158; Wed, 07 Jul 2010 10:31:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.93.3 with HTTP; Wed, 7 Jul 2010 10:31:11 -0700 (PDT)
In-Reply-To: <AANLkTimY78I-0BC94XVSffwe-sS3HKamXzX39pj04JKE@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> <AANLkTimY78I-0BC94XVSffwe-sS3HKamXzX39pj04JKE@mail.gmail.com>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Wed, 07 Jul 2010 10:31:11 -0700
Message-ID: <AANLkTiln5m_ZxSfp6Kt_1Za53E-902gFIHCko_Xj0RN_@mail.gmail.com>
To: Michael D Adams <mike@automattic.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] 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 17:37:05 -0000

On Wed, Jul 7, 2010 at 1:10 AM, Michael D Adams <mike@automattic.com> wrote:
> 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.

As far as I can tell pretty permalinks also use mod_rewrite so the PHP
code still sees the query parameter.

Yes, chances for conflict are very small, I agree.

Marius

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