RFC 2388, "Returning Values from Forms: multipart/form-data", August 1998

Note: This RFC has been obsoleted by RFC 7578

Errata ID: 5410
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Sébastien Puyet
Date Reported: 2018-06-26
Held for Document Update by: Alexey Melnikov
Date Held: 2018-07-26

Section 4.1 says:

   As with other multipart types, a boundary is selected that does not
   occur in any of the data. Each field of the form is sent, in the
   order defined by the sending appliction and form, as a part of the
   multipart stream.  Each part identifies the INPUT name within the
   original form. Each part should be labelled with an appropriate
   content-type if the media type is known (e.g., inferred from the file
   extension or operating system typing information) or as
   "application/octet-stream".

It should say:

   As with other multipart types, a boundary is selected that does not
   occur in any of the data. Each field of the form is sent, in the
   order defined by the sending application and form, as a part of the
   multipart stream.  Each part identifies the INPUT name within the
   original form. Each part should be labelled with an appropriate
   content-type if the media type is known (e.g., inferred from the file
   extension or operating system typing information) or as
   "application/octet-stream".

Notes:

A typo is present in the second sentence, the word "appliction" should be "application".

Alexey: why this is correct, this is unlikely to get readers confused. So marking it as "held for document update".

Report New Errata