Re: [http-state] Is this an omission in the parser rules of draft-ietf-httpstate-cookie-21?

Adam Barth <ietf@adambarth.com> Thu, 03 February 2011 20:15 UTC

Return-Path: <ietf@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 5C4A73A6A1D for <http-state@core3.amsl.com>; Thu, 3 Feb 2011 12:15:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.702
X-Spam-Level:
X-Spam-Status: No, score=-3.702 tagged_above=-999 required=5 tests=[AWL=-0.725, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 UvSLGMHDoMSd for <http-state@core3.amsl.com>; Thu, 3 Feb 2011 12:15:53 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 540DB3A6955 for <http-state@ietf.org>; Thu, 3 Feb 2011 12:15:53 -0800 (PST)
Received: by fxm9 with SMTP id 9so1694833fxm.31 for <http-state@ietf.org>; Thu, 03 Feb 2011 12:19:16 -0800 (PST)
Received: by 10.223.70.136 with SMTP id d8mr4628289faj.3.1296764355916; Thu, 03 Feb 2011 12:19:15 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by mx.google.com with ESMTPS id f24sm470429fak.0.2011.02.03.12.19.14 (version=SSLv3 cipher=RC4-MD5); Thu, 03 Feb 2011 12:19:14 -0800 (PST)
Received: by iwc10 with SMTP id 10so1584813iwc.31 for <http-state@ietf.org>; Thu, 03 Feb 2011 12:19:13 -0800 (PST)
Received: by 10.231.11.68 with SMTP id s4mr12282985ibs.14.1296764353201; Thu, 03 Feb 2011 12:19:13 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.35.13 with HTTP; Thu, 3 Feb 2011 12:18:43 -0800 (PST)
In-Reply-To: <20110202190453.f00013ceab8fb1928885c5c172fbfd4a.158515956e.wbe@email00.secureserver.net>
References: <20110202190453.f00013ceab8fb1928885c5c172fbfd4a.158515956e.wbe@email00.secureserver.net>
From: Adam Barth <ietf@adambarth.com>
Date: Thu, 3 Feb 2011 12:18:43 -0800
Message-ID: <AANLkTimdPgsxJQ+R3GzraPmgvxBevvbGnMQgrGaDDKjW@mail.gmail.com>
To: Remy Lebeau <remy@lebeausoftware.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: http-state@ietf.org
Subject: Re: [http-state] Is this an omission in the parser rules of draft-ietf-httpstate-cookie-21?
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: Thu, 03 Feb 2011 20:15:54 -0000

It's not an omission.  The use of quotation mark for cookie values in
RFC 2109 do not reflect how cookie behave in actual use.

Adam


On Wed, Feb 2, 2011 at 6:04 PM, Remy Lebeau <remy@lebeausoftware.org>; wrote:
> RFC 2109 allows cookie and attribute values to be wrapped in quotation
> marks, but ietf-httpstate-cookie-21's definitions of "cookie-value" and
> "cookie-av" do not seem to allow for that.  Or am I missing something?
> The examples in RFC 2109 fail to parse properly if the draft definitions
> are strictly used (for instance, processing a "Path" attribute can fail
> because the first character may be <"> instead of "/" unless <'>
> characters are stripped off during parsing).
>
> Also in the draft, "cookie-value" is defined as:
>
>  cookie-value      = token / ""
>
> Is the <""> portion a typo, or was it meant to be more like this
> instead?
>
>  cookie-value      = token / <"> token <">
>
> _______________________________________________
> http-state mailing list
> http-state@ietf.org
> https://www.ietf.org/mailman/listinfo/http-state
>