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

"Remy Lebeau" <remy@lebeausoftware.org> Fri, 04 February 2011 18:44 UTC

Return-Path: <remy@lebeausoftware.org>
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 08DA03A6A1E for <http-state@core3.amsl.com>; Fri, 4 Feb 2011 10:44:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 HLUeR55M1-8D for <http-state@core3.amsl.com>; Fri, 4 Feb 2011 10:44:10 -0800 (PST)
Received: from smtpoutwbe02.prod.mesa1.secureserver.net (smtpoutwbe02.prod.mesa1.secureserver.net [208.109.78.113]) by core3.amsl.com (Postfix) with SMTP id 435223A694A for <http-state@ietf.org>; Fri, 4 Feb 2011 10:44:10 -0800 (PST)
Received: (qmail 14291 invoked from network); 4 Feb 2011 18:47:35 -0000
Received: from unknown (HELO mm01.prod.mesa1.secureserver.net) (208.109.138.1) by smtpoutwbe02.prod.mesa1.secureserver.net with SMTP; 4 Feb 2011 18:47:35 -0000
Received: (qmail 26024 invoked by uid 99); 4 Feb 2011 18:47:35 -0000
Message-ID: <20110204184735.26023.qmail@mm01.prod.mesa1.secureserver.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_a13b852c45b1f1190c852fd5d5b8df13"
Message_ID: <20110204114735.f00013ceab8fb1928885c5c172fbfd4a.282673bda5.wbe@mobilemail.secureserver.net>
From: "Remy Lebeau" <remy@lebeausoftware.org>
To: ietf@adambarth.com, http-state@ietf.org
Date: Fri, 04 Feb 2011 11:47:35 -0700
X-Originating-IP: 76.93.119.83
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: Fri, 04 Feb 2011 18:44:11 -0000

-------- Original Message --------
Subject: Re: [http-state] Is this an omission in the parser rules of
draft-ietf-httpstate-cookie-21?
From: Adam Barth <ietf@adambarth.com>;
Date: Fri, February 04, 2011 10:19 am
To: Remy Lebeau <remy@lebeausoftware.org>;
Cc: http-state@ietf.org

> The draft gives user agents precise 
> instructions for how to parse all
> manner of cookies, including cookies with
> values that contain quote characters.  That 
> information is contained in Section 5

I have re-read Section 5 and I do not see its grammar or parsing rules
accounting for quoted-string values at all. It only says to remove WSP
characters surrounding extracted names and values, and quote characters
are not part of the WSP definition. So what am I missing? Where exactly
does it say how to unquote a quoted-string used in attribute values?