Re: [http-state] Ticket 6: host-only cookies

Adam Barth <ietf@adambarth.com> Tue, 02 February 2010 17:12 UTC

Return-Path: <adam@adambarth.com>
X-Original-To: http-state@core3.amsl.com
Delivered-To: http-state@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 15E4F3A694A for <http-state@core3.amsl.com>; Tue, 2 Feb 2010 09:12:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level:
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[AWL=0.088, 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 q3G-wD7GvVVG for <http-state@core3.amsl.com>; Tue, 2 Feb 2010 09:12:50 -0800 (PST)
Received: from mail-pz0-f183.google.com (mail-pz0-f183.google.com [209.85.222.183]) by core3.amsl.com (Postfix) with ESMTP id 09E863A6857 for <http-state@ietf.org>; Tue, 2 Feb 2010 09:12:49 -0800 (PST)
Received: by pzk13 with SMTP id 13so329082pzk.32 for <http-state@ietf.org>; Tue, 02 Feb 2010 09:13:26 -0800 (PST)
MIME-Version: 1.0
Received: by 10.142.248.28 with SMTP id v28mr708672wfh.203.1265130806109; Tue, 02 Feb 2010 09:13:26 -0800 (PST)
In-Reply-To: <4B6854C8.4040602@kristol.org>
References: <7789133a1001220050m56cc438x35099b7972639331@mail.gmail.com> <4B59B834.3030500@gmail.com> <4C374A2653EB5E43AF886CE70DFC567213CE9BE2B4@34093-MBX-C03.mex07a.mlsrvr.com> <7789133a1002012300k4627d9a2sad7f5b776c544487@mail.gmail.com> <4B6854C8.4040602@kristol.org>
From: Adam Barth <ietf@adambarth.com>
Date: Tue, 2 Feb 2010 09:13:06 -0800
Message-ID: <7789133a1002020913p13f48804x1174904f3eec9c7d@mail.gmail.com>
To: Dave Kristol <dmk-http-state@kristol.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: http-state <http-state@ietf.org>
Subject: Re: [http-state] Ticket 6: host-only cookies
X-BeenThere: http-state@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discuss HTTP State Management Mechanism <http-state.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/http-state>, <mailto:http-state-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/http-state>
List-Post: <mailto:http-state@ietf.org>
List-Help: <mailto:http-state-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-state>, <mailto:http-state-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Feb 2010 17:12:51 -0000

On Tue, Feb 2, 2010 at 8:37 AM, Dave Kristol <dmk-http-state@kristol.org> wrote:
> Adam Barth wrote:
>>
>> I've added the following text to the server section, as recommend by
>> Dan Winship:
>>
>>              <t>WARNING: Some legacy user agents treat an absent Domain
>>              attribute as if the Domain attribute were present and
>> contained
>>              the current host name. For example, if example.com returns a
>>              Set-Cookie header without a Domain attribute, these user
>> agents
>>              will send the cookie to www.example.com.</t>
>
> If the implied Domain attribute is example.com, then the user agent may only
> return the cookie to example.com.

Do you mean that

Set-Cookie: foo=bar; Domain=example.com

and

Set-Cookie: foo=bar; Domain=.example.com

are treated differently by user agents?  That might be true according
to 2109 (I'd have to check), but I don't think that's how user agents
work in practice.  They appear to ignore the leading dot.  If you have
a test case that show a difference, I'd be very interested in seeing
it.

Adam