[Fwd: 2047 in 2388: encoded words in multipart/form-data]

FYI -- see Sebastien's question below, posted on the IETF apps-discuss 
mailing list.

Is there a specification/interop problem with respect to header encoding 
in multipart/form-data?

Best regards, Julian

-------- Original Message --------
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, 7 Jan 2010 14:40:43 +0000
MIME-Version: 	1.0
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>
Content-Type: 	multipart/mixed; boundary="===============0097767713=="
Sender: 	apps-discuss-bounces@ietf.org
Errors-To: 	apps-discuss-bounces@ietf.org
X-GMX-Antivirus: 	0 (no virus found)
X-GMX-Antispam: 	0 (Mail was not recognized as spam);
Detail=5D7Q89H36p7lX4jf99LhzfQ6D7mSm2itl7bz4bcJZCOzcffmVJ7A3JYNSnW8OkSDNTwcD 

FWy0GwUJFWqd6BrGWOyMU2PGnwnZHKVpe9cxkY2bhleZXKllVSgS/68lKowkouaEK5BcU1Kwd2fj 

N3J1w==V1;
X-GMX-UID: 	ip8nHz1SbXBsw/BLLzQ2Fd4qLyUmZQj6



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

_______________________________________________
Apps-Discuss mailing list
Apps-Discuss@ietf.org
https://www.ietf.org/mailman/listinfo/apps-discuss