Re: obs-text character encoding and error handling; duplicate parameter names in Content-Type

"Peter Occil" <poccil14@gmail.com> Sat, 25 May 2013 07:49 UTC

Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 135C221F8607 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 25 May 2013 00:49:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.242
X-Spam-Level:
X-Spam-Status: No, score=-10.242 tagged_above=-999 required=5 tests=[AWL=0.356, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BkQgiBnUbwMv for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 25 May 2013 00:49:45 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 71CE021F937B for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sat, 25 May 2013 00:49:45 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1Ug9DI-0001jw-BI for ietf-http-wg-dist@listhub.w3.org; Sat, 25 May 2013 07:48:28 +0000
Resent-Date: Sat, 25 May 2013 07:48:28 +0000
Resent-Message-Id: <E1Ug9DI-0001jw-BI@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <poccil14@gmail.com>) id 1Ug9D3-0001j0-4x for ietf-http-wg@listhub.w3.org; Sat, 25 May 2013 07:48:13 +0000
Received: from mail-ye0-f174.google.com ([209.85.213.174]) by lisa.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <poccil14@gmail.com>) id 1Ug9Cy-0004r7-M8 for ietf-http-wg@w3.org; Sat, 25 May 2013 07:48:13 +0000
Received: by mail-ye0-f174.google.com with SMTP id r9so490870yen.5 for <ietf-http-wg@w3.org>; Sat, 25 May 2013 00:47:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:from:to:references:in-reply-to:subject:date:mime-version :content-type:x-priority:x-msmail-priority:importance:x-mailer :x-mimeole; bh=N2sdDVYVJWcDgvtBJRz7Ytz8SJgP5Q5NRuDbUR91eF8=; b=cNdUoHzQK/DUVmdsRsyZj3Qni3H37n3iZSc/rg5rJzPF3w20e8w1T6NViTGza9H57M sfUha6NoRHDVc22LmnZZ0IBs2k1WS6yoPU/7YSgtcTSii1QatpA72N+y9mHQI+F6k0Wj EL5InMpbfbpy3L3/pugUfdW52z/S+k71Mn00bMRdewHwIJfLkk7AXXLkC0Fbp0UpVlQG 95z/8k6EmOElyQzr23qLXy5SEJhEOmSMu65RqkJNXWPvvgbIQd3V7hMz1p3nbaM0DpyO rB5vkmFLKc5l4Ideoj/TnXsqlqPr5rSXpLq+CjqQVNhg0FZXdRcmeVIbcrEH067RaW2K GzLQ==
X-Received: by 10.236.136.138 with SMTP id w10mr11436881yhi.129.1369468063039; Sat, 25 May 2013 00:47:43 -0700 (PDT)
Received: from PeterPC (c-76-119-210-197.hsd1.ma.comcast.net. [76.119.210.197]) by mx.google.com with ESMTPSA id n15sm28512245yhi.2.2013.05.25.00.47.41 for <ietf-http-wg@w3.org> (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 25 May 2013 00:47:42 -0700 (PDT)
Message-ID: <C66D8DCFE7C341A79B0A091B509BFB3C@PeterPC>
From: "Peter Occil" <poccil14@gmail.com>
To: "HTTP Working Group" <ietf-http-wg@w3.org>
References: <F2550CB07E9B440F9AC001D3038A634C@PeterPC> <83535E5464C242B1A0612D300F4F87CF@PeterPC>
In-Reply-To: <83535E5464C242B1A0612D300F4F87CF@PeterPC>
Date: Sat, 25 May 2013 03:47:36 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01E3_01CE58FA.984F5F90"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 15.4.3555.308
X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3555.308
Received-SPF: pass client-ip=209.85.213.174; envelope-from=poccil14@gmail.com; helo=mail-ye0-f174.google.com
X-W3C-Hub-Spam-Status: No, score=-3.1
X-W3C-Hub-Spam-Report: AWL=-2.506, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1Ug9Cy-0004r7-M8 f75a04e76835463a3e5a3b21b5920592
X-Original-To: ietf-http-wg@w3.org
Subject: Re: obs-text character encoding and error handling; duplicate parameter names in Content-Type
Archived-At: <http://www.w3.org/mid/C66D8DCFE7C341A79B0A091B509BFB3C@PeterPC>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18088
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

On issue 2, I found the following in RFC6838: “It is an error for a specific parameter to be specified more than once.” So that issue is resolved.  It would be helpful to refer to that in the specification.

From: Peter Occil 
Sent: Saturday, May 25, 2013 3:30 AM
To: HTTP Working Group 
Subject: Re: obs-text character encoding and error handling; duplicate parameter names in Content-Type

On issue 1, I guess I was only reading the 22 version; in the latest version it says “Recipients SHOULD treat other octets in field content (obs-text) as opaque data”. If that’s the case, it should also say that the behavior of converting field values containing obs-text to Unicode strings (particularly parameter values in Content-Type) is undefined.

Issue 2 still stands.

From: Peter Occil 
Sent: Saturday, May 25, 2013 3:14 AM
To: HTTP Working Group 
Subject: obs-text character encoding and error handling; duplicate parameter names in Content-Type

obs-text character encoding and error handling; duplicate parameter names in Content-Type

I have two issues.

1. obs-text character encoding and error handling

What is the character encoding used when a header field value contains obs-text, and particularly
parameter values in Content-Type?  Is it ISO-8859-1, UTF-8, or something else?  Or is the encoding
  undefined?  Error handling rules for obs-text, unlike for obs-fold, are also absent.

2. Duplicate parameter names in Content-Type

Suppose that the following Content-Type is received:

    text/html; charset=iso-8859-1; charset=utf-8
What is the resulting value of the charset parameter?  Is it iso-8859-1, utf-8, an error, or undefined?
(This issue also applies to Content-Disposition, Accept, and other header fields that use parameters.)
--Peter