2047 in 2388: encoded words in multipart/form-data
"Sebastien Lambla" <seb@serialseb.com> Thu, 07 January 2010 14:40 UTC
Return-Path: <seb@serialseb.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4A7E73A6853 for <apps-discuss@core3.amsl.com>; Thu, 7 Jan 2010 06:40:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.184
X-Spam-Level:
X-Spam-Status: No, score=-0.184 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, 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 UpaNOdefPffp for <apps-discuss@core3.amsl.com>; Thu, 7 Jan 2010 06:40:46 -0800 (PST)
Received: from blu0-omc3-s32.blu0.hotmail.com (blu0-omc3-s32.blu0.hotmail.com [65.55.116.107]) by core3.amsl.com (Postfix) with ESMTP id D8D593A6810 for <apps-discuss@ietf.org>; Thu, 7 Jan 2010 06:40:45 -0800 (PST)
Received: from BLU102-DS6 ([65.55.116.74]) by blu0-omc3-s32.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 7 Jan 2010 06:40:44 -0800
X-Originating-IP: [78.105.1.95]
X-Originating-Email: [seb@serialseb.com]
Message-ID: <BLU102-DS695C704E48B280FF87F3CB5710@phx.gbl>
From: Sebastien Lambla <seb@serialseb.com>
To: apps-discuss@ietf.org
Subject: 2047 in 2388: encoded words in multipart/form-data
Date: Thu, 07 Jan 2010 14:40:43 +0000
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0288_01CA8FA7.64685530"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcqPp2QtSI++PVvuQdOnMM1eioennA==
Content-Language: en-gb
X-OriginalArrivalTime: 07 Jan 2010 14:40:44.0358 (UTC) FILETIME=[64999E60:01CA8FA7]
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jan 2010 14:42:40 -0000
All, There seems to be an issue with 2388 describing multipart/form-data. It says that the field name (aka the name= parameter) has to be encoded using 2047 when containing non-ascii characters. As I understand it, the filename parameter itself is to be encoded with 2231, and 2047 specifically states that it is not to be used in parameters. So there's a clash between 2047 and 2388, which should probably be addressed. In the mean-time, I'd like to know if anyone has been known to use 2047 for parameters? I've quickly tested browser implementations, and they simply pass back the UTF-8 code points I've provided in the markup, which I find very surprising. How do people deal with such code-points in the headers? Thanks, Sebastien Lambla
- 2047 in 2388: encoded words in multipart/form-data Sebastien Lambla