Re: [OAUTH-WG] Basic questions about using the HTTP Authorization header
Brian Eaton <beaton@google.com> Sun, 11 July 2010 06:49 UTC
Return-Path: <beaton@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 410F43A68B6 for <oauth@core3.amsl.com>; Sat, 10 Jul 2010 23:49:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.676
X-Spam-Level:
X-Spam-Status: No, score=-101.676 tagged_above=-999 required=5 tests=[AWL=0.301, 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 lAYmaxX03VCM for <oauth@core3.amsl.com>; Sat, 10 Jul 2010 23:49:45 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id 3C6123A6768 for <oauth@ietf.org>; Sat, 10 Jul 2010 23:49:45 -0700 (PDT)
Received: from kpbe14.cbf.corp.google.com (kpbe14.cbf.corp.google.com [172.25.105.78]) by smtp-out.google.com with ESMTP id o6B6noLA006292 for <oauth@ietf.org>; Sat, 10 Jul 2010 23:49:50 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1278830990; bh=18ocgujYlIbkXrxu1qh/OHarAjk=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type:Content-Transfer-Encoding; b=aS1MnBK6+p/uQ0u0IH0PH7Do+0CW32UXUBA75JAZW/sRSvGJe0p+cpNQHpHUCiQZQ BFBEDR9oXaYu2TyixZFKw==
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=Jnsl51d+r4HsHKpzbwM6PIVHUsx8fk/7VgX6G+gYe/soMFEM3Y5j3WUtWZzQa+P0b V7Q5oXG1LW5OLCiOt2G6g==
Received: from pzk3 (pzk3.prod.google.com [10.243.19.131]) by kpbe14.cbf.corp.google.com with ESMTP id o6B6nmxB030041 for <oauth@ietf.org>; Sat, 10 Jul 2010 23:49:48 -0700
Received: by pzk3 with SMTP id 3so885941pzk.8 for <oauth@ietf.org>; Sat, 10 Jul 2010 23:49:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.48.18 with SMTP id v18mr14299928wfv.102.1278830988267; Sat, 10 Jul 2010 23:49:48 -0700 (PDT)
Received: by 10.142.193.19 with HTTP; Sat, 10 Jul 2010 23:49:48 -0700 (PDT)
In-Reply-To: <AANLkTil3IQ7JloXmFeh_wydfAtkrhNADUhqjj_cqVOh2@mail.gmail.com>
References: <AANLkTilHhGQvsuvxfFF1e6zhOL7ldiqCHlrbuX47KBPV@mail.gmail.com> <012AB2B223CB3F4BB846962876F47217059B6711@SNV-EXVS08.ds.corp.yahoo.com> <AANLkTil3IQ7JloXmFeh_wydfAtkrhNADUhqjj_cqVOh2@mail.gmail.com>
Date: Sat, 10 Jul 2010 23:49:48 -0700
Message-ID: <AANLkTil5RfwCRPymMdf_XfuH64bZa6hZC_CZEtkOn8jz@mail.gmail.com>
From: Brian Eaton <beaton@google.com>
To: Andrew Arnott <andrewarnott@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
Cc: oauth <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Basic questions about using the HTTP Authorization header
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: Sun, 11 Jul 2010 06:49:46 -0000
On Sat, Jul 10, 2010 at 10:41 PM, Andrew Arnott <andrewarnott@gmail.com> wrote: > Eran, > Is the draft 10 spec going to outline what characters are allowed in the > access token? And if not (or if all characters are allowed), is it going to > include details about (or a reference to a doc about) how to properly escape > the access token when specifying it in the HTTP Authorization header? Just sent a proposal to the list to drop the Authorization header name="value" syntax completely. We can copy what Basic/NTLM/Negotiate have been doing instead.
- [OAUTH-WG] Basic questions about using the HTTP A… Andrew Arnott
- Re: [OAUTH-WG] Basic questions about using the HT… William Mills
- Re: [OAUTH-WG] Basic questions about using the HT… Andrew Arnott
- Re: [OAUTH-WG] Basic questions about using the HT… Brian Eaton