RFC Errata
Found 2 records.
Status: Verified (1)
RFC 7578, "Returning Values from Forms: multipart/form-data", July 2015
Source of RFC: appsawg (art)
Errata ID: 4676
Status: Verified
Type: Technical
Reported By: Egon Eckert
Date Reported: 2016-04-26
Verifier Name: Alexey Melnikov
Date Verified: 2016-04-26
Section 4.6. says:
--AaB03x content-disposition: form-data; name="_charset_" iso-8859-1 --AaB03x-- content-disposition: form-data; name="field1" ...text encoded in iso-8859-1 ... AaB03x--
It should say:
--AaB03x content-disposition: form-data; name="_charset_" iso-8859-1 --AaB03x content-disposition: form-data; name="field1" ...text encoded in iso-8859-1 ... --AaB03x--
Notes:
Boundary hyphens were misplaced, I think. The second boundary delimiter should not have them on the end of the line, and the last boundary delimiter should have them on the beginning of the line too.
Status: Reported (1)
RFC 7578, "Returning Values from Forms: multipart/form-data", July 2015
Source of RFC: appsawg (art)
Errata ID: 5616
Status: Reported
Type: Technical
Reported By: Philip McGrath
Date Reported: 2019-01-30
Section 4.5 says:
For example, a form with a text field in which a user typed "Joe owes <eu>100", where <eu> is the Euro symbol, might have form data returned as: --AaB03x content-disposition: form-data; name="field1" content-type: text/plain;charset=UTF-8 content-transfer-encoding: quoted-printable Joe owes =E2=82=AC100. --AaB03x
It should say:
For example, a form with a text field in which a user typed "Joe owes <eu>100", where <eu> is the Euro symbol, might have form data returned as: --AaB03x content-disposition: form-data; name="field1" content-type: text/plain;charset=UTF-8 content-transfer-encoding: quoted-printable Joe owes <eu>100. --AaB03x
Notes:
Section 4.7 says that "Senders SHOULD NOT generate any parts with a Content-Transfer-Encoding header field."