[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

LYNX-DEV A note on the multipart/form-data code

From: Klaus Weide
Subject: LYNX-DEV A note on the multipart/form-data code
Date: Sat, 23 Nov 1996 19:09:43 -0600 (CST)

 I had a look at the GridText.c from Hiram's latest composite package,
which includes Fote's recently added code for POSTing form data with
Content-Type multipart/form-data.  I haven't compiled it yet, but
here is a note on how the charset parameter is handled which may be
added by that code:

 According to the HTML i18n draft, RFC 1867, and more generally the
MIME specs, the charset parameter (if appropriate) should go on
separate Content-Type headers for each of the individual form fields,
not on the enclosing multipart/form-data Content-Type header.
In fact, that seems to be one reason why mp/form-data is better for
i18n than mp/x-w-f-u - different form fields could be encoded 
in different charsets etc.

 Not tested, but a MIME-aware mail client which encounters a message
with the charset parameter in the wrong place would probably also not
apply it to the individual body parts.  (charset parameter is defined
in MIME specs only for text/* types AFAIK.  multipart/<unknown-subtype>
is supposed to be treated like multipart/mixed.)



; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]