MHonArc v2.5.2 -->

















ebxml-msg message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [Elist Home]








Subject: RE: [ebxml-msg] MIME prolog, epilog issue




From: Dick Brooks <dick@systrends.com>
To: Matthew MacKenzie <matt@xmlglobal.com>, ebxml-msg@lists.oasis-open.org
Date: Tue, 22 Oct 2002 09:42:29 -0700






Title: [ebxml-msg] MIME prolog, epilog issue



Matt,
 
In the 
case of an HTTP 1.1 binding, RFC2616 explicitly states:
 
"  Unlike in RFC 2046, the epilogue of any multipart 
message MUST be
   empty; HTTP applications MUST NOT transmit the 
epilogue (even if the
   original multipart contains an 
epilogue)."
 
Unfortunately I didn't see any reference to the handling of a prolog. 
IMO, the prolog should be treated the same as the epilogue.
 
Dick Brooks
Systrends, Inc
7855 South River Parkway, Suite 
111
Tempe, Arizona 85284
Web: www.systrends.com <http://www.systrends.com>
Phone:480.756.6777,Mobile:602-684-1484,eFax:240-352-0714