bildwelt
E2E FORUM
E2E Bridge E2E Commerce

Reply To: Soap with attachment

E2E Forum Modeling & Development Soap with attachment Reply To: Soap with attachment

#2016

Alfred
Moderator

I can reproduce the issue. The interesting part of your log file is:

 [2015-09-22 09:17:09 +0200][0000000005][Debug][External][CURL][SendHeader][POST /... HTTP/1.1
 Host: ...
 Accept: */*
 SOAPAction: "InjectFile_1.0"
 Mime-Version: 1.0
 Content-Type: multipart/related; boundary="00000009f3e9c5a000000dd400000c20c92bfc29"; type="application/soap+xml"; start="cid:00000008f3e9c5a000000dd400000c20c92bfc29"
 Content-Length: 2616
 Expect: 100-continue
 ]
 [2015-09-22 09:17:09 +0200][0000000005][Debug][External][CURL][ReceiveHeader][HTTP/1.1 100 Continue]
 [2015-09-22 09:17:09 +0200][0000000005][Debug][External][CURL][SendData][--00000009f3e9c5a000000dd400000c20c92bfc29
 Content-Type: application/soap+xml
 Content-ID: 00000008f3e9c5a000000dd400000c20c92bfc29
 Content-Transfer-Encoding: base64
 PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4KPGVudjpFbnZlbG9wZSB4bWxu
 ...

but two headers should have these values

 Content-Type: application/soap+xml; charset="utf-8"
 Content-Transfer-Encoding: 8bit

and the text should be not base64 encoded.

You can try a workaround and change the tag soapVersion to 1.1 instead of 1.2 on the <<SOAPAlias>>. In this case the SOAP
part encoding is correct. But be aware that the Content-Type will change to text/xml.

We will inform you when a fix is available.