Re: [http-state] [httpstate] #11: Consider defining how to map a cookie-string into unicode

"httpstate issue tracker" <trac@tools.ietf.org> Wed, 10 March 2010 23:19 UTC

Return-Path: <trac@tools.ietf.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 BD9873A6956 for <http-state@core3.amsl.com>; Wed, 10 Mar 2010 15:19:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.489
X-Spam-Level:
X-Spam-Status: No, score=-102.489 tagged_above=-999 required=5 tests=[AWL=0.111, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 yoiMxUEDexbz for <http-state@core3.amsl.com>; Wed, 10 Mar 2010 15:19:04 -0800 (PST)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id BFFBC3A690C for <http-state@ietf.org>; Wed, 10 Mar 2010 15:19:02 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <trac@tools.ietf.org>) id 1NpVBD-00023v-MD; Wed, 10 Mar 2010 15:19:07 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "httpstate issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.6
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.6, by Edgewall Software
To: ietf@adambarth.com
X-Trac-Project: httpstate
Date: Wed, 10 Mar 2010 23:19:07 -0000
X-URL: http://tools.ietf.org/httpstate/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/httpstate/trac/ticket/11#comment:1
Message-ID: <071.e0b5df3d3c55e1e3310622ce8f701733@tools.ietf.org>
References: <062.544c0bb072716f6c8dcb113edd607a66@tools.ietf.org>
X-Trac-Ticket-ID: 11
In-Reply-To: <062.544c0bb072716f6c8dcb113edd607a66@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: ietf@adambarth.com, http-state@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
X-Mailman-Approved-At: Thu, 11 Mar 2010 13:52:03 -0800
Cc: http-state@ietf.org
Subject: Re: [http-state] [httpstate] #11: Consider defining how to map a cookie-string into unicode
X-BeenThere: http-state@ietf.org
X-Mailman-Version: 2.1.9
Reply-To: trac@localhost.amsl.com
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: Wed, 10 Mar 2010 23:19:07 -0000

#11: Consider defining how to map a cookie-string into unicode
--------------------------------+-------------------------------------------
 Reporter:  ietf@…              |        Owner:        
     Type:  defect              |       Status:  closed
 Priority:  major               |    Milestone:        
Component:  cookie              |      Version:        
 Severity:  -                   |   Resolution:  fixed 
 Keywords:                      |  
--------------------------------+-------------------------------------------
Changes (by ietf@…):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 As discussed on the list:

 The draft treats the cookie values as opaque octets throughout for use
 on the wire.  I've added a SHOULD-level requirement to use a UTF8 when
 converting the octets to characters (e.g., for use in the user agent's
 user interface).

 Given that the encoding issue doesn't appear to affect
 interoperability on the wire, I think a SHOULD-level recommendation is
 appropriate here.  If specific APIs (e.g., document.cookie) have more
 specific needs, they can add additional requirements.

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/httpstate/trac/ticket/11#comment:1>
httpstate <http://tools.ietf.org/httpstate/>