Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
For form/multipart-data, I’ve seen input that has the form =[2 to 6 hex chars].
I’m wondering which RFC defines it?
I want to encode non-file form data to a binary char stream so that iconv doesn’t produce bad output. I reckon the behavior is similar to formurl-encoded decoding.
multipart/form-datais based on RFC 2045 and RFC 2046, formalized in RFC 2388, and included in W3C standards HTML40 Section 13.4 and HTML5 Section 4.10.22.6. The encoding you are seeing is MIME’squoted-printableencoding, which is defined in RFC 2045 Section 6.7. Thequoted-printableencoding operates on byte octets, and thus will ALWAYS contain 2 hex characters after a=character (except for “soft” line breaks, which consist of a=character followed by a CRLF line break).