RFC 2049: in the example given, --unique-boundary-2 ...

Internet RFC Index

Usenet FAQ Index

Other FAQs

Documents

Search
  Search FAQs
  Search RFCs

 
Reader comments:
 

Comment by Irwin
Submitted on 12/13/2005
Related RFC: RFC 2049
Rating: Not yet rated	Rate this comment: N/A Worst Weak OK Good Great
in the example given,      --unique-boundary-2      Content-Type: audio/basic      Content-Transfer-Encoding: base64 is shown as a valid MIME header definition. Is this correct? Is it not required that there be a blank like between mime part header and body? and it that is the case, wouldnt Content-Transfer-Encoding be interpreted as part of the body?

 
 
FAQS.ORG makes no guarantees as to the accuracy of the posts. Each post is the personal opinion of the poster. These posts are not intended to substitute for medical, tax, legal, investment, accounting, or other professional advice. FAQS.ORG does not endorse any opinion or any product or service mentioned mentioned in these posts.

<< Back to: RFC 2049