Soap message (multipart MIME message) with (+) attachment...

Discussion forum about all things Team Developer 7.x
Posts: 16
Joined: 10 Mar 2017, 07:41
Location: Tallinn, Estonia

Soap message (multipart MIME message) with (+) attachment...

Post by Riuks » 19 Sep 2019, 12:29

I have an issue with goverment soap: i need to send attatcment - binary data, something mystical MIME_boundary and so on. As far i undestand inside soap envelope is refference and binary data will transvered after soap envelope.
As far i understand right after envelope (not in xml , not between envelope tags) but my experience is only „inside envelope“ .

Right now i have no glue how to define this attachment part.

I also used wsdl-wizard and TD puts binary
<tdwsns:file href="cid:refference">HERE</tdwsns:file>

Sample (Annex F):
.. other transport headers ...
Content-Type: multipart/related; type="text/xml"; start="<rootpart>"; boundary="MIME_boundary"
MIME-Version: 1.0

Content-Type: text/xml; charset=UTF-8
Content-Transfer-Encoding: 8bit
Content-ID: <rootpart>

<?xml version="1.0" encoding="UTF-8"?>
<xrd:client id:objectType="SUBSYSTEM">
<xrd:service id:objectType="SERVICE">

Content-Type: application/octet-stream; name=data.bin
Content-Transfer-Encoding: base64
Content-ID: <data.bin>
Content-Disposition: attachment; name="data.bin"; filename="data.bin"


So, question :is multipart/mixed and swa supported somehow doable with TD soap reguest?
Hope someone knows , or at least any idea...


Additional info: ... ttachments :
2.4 Attachments
In case the message has attachments, it MUST be formatted as a multipart MIME message, with the SOAP request and its attachments being separate parts of the message. The SOAP request must be the first part. The resulting MIME message MUST be structured in accordance with the specification for SOAP messages with attachments [SOAPATT] and the request SOAP part's Content-Transfer-Encoding MIME header value MUST be "8bit". MIME headers of each part of the message are preserved without modification in the security server. For an example request that contains attachments see Annex F.
Additionally, MTOM-encoded [MTOM] messages are supported in the security server – the security server accepts MIME multipart messages where the content-type of the SOAP part is "application/xop+xml". ... ments.html ... guide.html

Return to “General Discussion”

Who is online

Users browsing this forum: [Ccbot], monchotgu and 0 guests