Re: [http-state] Ticket 5: Cookie ordering

Dan Witte <> Sat, 06 February 2010 00:03 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C1D413A6E83 for <>; Fri, 5 Feb 2010 16:03:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Dp7fB31Sqqb7 for <>; Fri, 5 Feb 2010 16:03:54 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 8091C3A6996 for <>; Fri, 5 Feb 2010 16:03:54 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 2754E17FC118; Fri, 5 Feb 2010 16:04:36 -0800 (PST)
Date: Fri, 5 Feb 2010 16:04:35 -0800 (PST)
From: Dan Witte <>
Message-ID: <>
In-Reply-To: <op.u7nnk8uyvqd7e2@killashandra.oslo.osa>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: []
X-Mailer: Zimbra 6.0.4_GA_2038.RHEL5_64 (ZimbraWebClient - FF3.0 (Linux)/6.0.4_GA_2038.RHEL5_64)
Cc: http-state <>
Subject: Re: [http-state] Ticket 5: Cookie ordering
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discuss HTTP State Management Mechanism <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 06 Feb 2010 00:03:57 -0000

----- "Yngve Nysaeter Pettersen" <> wrote:

> IOW, if ordering is determined by anything but the domain and path the
> sequence of cookie is going to vary depending on which servers the
> clients  
> visits and the sequence it visits them, and this might cause
> significant  
> problems for a server that considers ordering significant.

Indeed. In Firefox, we sort by path length and then creation time. I can't comment as to whether sites depend on it now, but at one point we did drop the creation time sort - and sites broke. has some details.

We also found that creation time should be persisted when cookies are modified. I don't have a bug reference handy for this one, but it could be dug up.

I like the idea of ordering by domain. Ultimately, having this stuff in a more storage-esque API where domain and path info are available in the Cookie header, or document.cookie, would make this much less of an issue...