I have looked at the mm7 spec. All their multipart/related messages end with the boundary in the header. I still am not sure if this is applies only to mm7 or not.
Would it be possible to change this behavior ? Or is it by design ? Regards Stefan. On Wed, 2007-01-03 at 08:25 +0200, Stefan Kok wrote: > I have noticed that when SWA sends a multipart/related message it looks > like: (Trimmed to keep it short) > > > POST /mm7 HTTP/1.1 > SOAPAction: "" > User-Agent: Axis2 > Content-Length: 37588 > Content-Type: multipart/related; > boundary=MIMEBoundaryurn_uuid_A9D5ECF2C417B3D84B11678015337975; > type="text/xml"; > start="<0.urn:uuid:[EMAIL PROTECTED]>"; > charset=UTF-8 > Authorization: Digest username="username", realm="somerealm", > nonce="RZs7zw==babe2df5bea49ce4", uri="/some", response="44a", qop=auth, > nc=00001, cnonce="e4c3c3", algorithm="MD5" > Host: fqdn:8080 > > --MIMEBoundaryurn_uuid_A9D5ECF2C417B3D84B11678015335343 > content-type: text/xml; charset=UTF-8 > content-transfer-encoding: 8bit > content-id: <0.urn:uuid:[EMAIL PROTECTED]> > > <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";><soapenv:Header><mm7:TransactionID > > xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-3"; > mustUnderstand="1">MyTransaction</mm7:TransactionID></soapenv:Header> > <soapenv:Body> > . > . > .<Content href="urn:uuid:A9D5ECF2C417B3D84B11678015319801" /> > </SubmitRequest> > </soapenv:Body> > </soapenv:Envelope> > --MIMEBoundaryurn_uuid_A9D5ECF2C417B3D84B11678015335343 > content-type: image/jpeg > content-transfer-encoding: binary > content-id: <urn:uuid:A9D5ECF2C417B3D84B11678015319801> > > ......JFIF.............>Exif..II*.......................ACD Systems > Digital Imaging.....ACD Systems Digital > Imaging.......d....".......................... > .. > .. > ...............("..&...#/#&)*---.!141+4(,-+..........@ > +$+@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@...% > 67U..............................................A..! > 1.Q.".Bq............?...E...,..o.pi=...R...F;....Mul0.d.. > .c......QK .R f..k....?n/.&.....o.K..X.....vN(.....8.....m..(. > --MIMEBoundaryurn_uuid_A9D5ECF2C417B3D84B11678015335343 > content-type: application/octet-stream > content-transfer-encoding: binary > content-id: <urn:uuid:A9D5ECF2C417B3D84B11678015321042> > > #!AMR > [EMAIL PROTECTED] > "X....IM.8L..:....Cl'[EMAIL PROTECTED]:.C[E..W.}..4S..,... > .u=Ge.&[EMAIL > PROTECTED]@.6b.Qs.N.....L....w....W..).\.A....{K"..gC.3.go.!......8.\'[EMAIL > PROTECTED]:[EMAIL PROTECTED]"....`...[T.KU. > --MIMEBoundaryurn_uuid_A9D5ECF2C417B3D84B11678015335343-- > > Should it not end something like: > > [EMAIL PROTECTED]"....`...[T.KU. > --MIMEBoundaryurn_uuid_A9D5ECF2C417B3D84B11678015335343-- > --boundary=MIMEBoundaryurn_uuid_A9D5ECF2C417B3D84B11678015337975-- [1] > > [1] Taken from the header. > > I have seen many samples with this format. I am not an expert but it > seems odd. > > Kind regards > Stefan. > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Stefan Kok <[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
