Next in thread → Next in month →

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

From
Dick Brooks <>
Date
2002-10-22T16:44:13+00:00
ID
Thread
RE: [ebxml-msg] MIME prolog, epilog issue
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
  

  
-----Original Message-----
From: Matthew MacKenzie 
  [mailto:]
Sent: Tuesday, October 22, 2002 9:32 
  AM
To: 
Subject: [ebxml-msg] 
  MIME prolog, epilog issue

  
Group: 

  
I've recently come across an issue where a prolog is included 
  in an  
ebxml message.  I believe that MIME 
  allows this, mostly for the benefit  
of ancient 
  mail user agents.  Should an ebXML MSH send/accept prologs  
  
or epilogs? 

  
It's my opinion that in this context a prolog is really 
  not  
appropriate, and I would like to see the 
  specification specifically  
forbid it. 

  
An example (part of a message I received recently): 

  
mime-version: 2.0 
content-type: 
  multipart/related; boundary="=_3DB3E4F8.506E8220_=" 
cookie: a=4 
soapaction: ebXML 
content-length: 3590 

  
This message is MIME format. Since your mail reader does 
  not 
understand this format, some or all of this 
  message may 
not be legible. 
--=_3DB3E4F8.506E8220_= 
Content-ID: 
  <-0> 
Content-Transfer-Encoding: ClearText 
Content-Type: text/xml 
Content-Disposition: 
  attachment; filename="SOAP.xml" 

  
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"  
  
xmlns:eb=" 
http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header- 
  
2_0.xsd"  xmlns 
:xlink="http://www.w3.org/1999/xlink"><SOAP:Header><eb:MessageHeader  
  
SOAP:mustUn 
derstand="1" 
  eb:version="2.0" ><eb:From><eb:PartyId   
  
eb:type="http://www.iso.int 
/schemas/eanucc/gln" >5060004470006</eb:PartyId> 
  
<eb:Role>http://www.ean-ucc.org/roles/buyer</eb:Role> 
  
</eb:From> 
... 

  
---------------------------------------------------------------- 
  
To subscribe or unsubscribe from this elist use the 
  subscription 
manager: <http://lists.oasis-open.org/ob/adm.pl>
Next in thread → Next in month →