Enable Service Manager to appropriately handle small attachments when using a .NET web service

Idea ID 2755738

Enable Service Manager to appropriately handle small attachments when using a .NET web service

Attachments smaller than 768 bytes, when submitted from a .NET web service to Service Manager, are base64 encoded and inserted into the SOAP message.  MTOM handles larger attachments using MIME parts.

When Service Manager receives the smaller attachments, they are attached with no content because SM doesn't look for the content in the SOAP message.  

We ask that Service Manager be updated to also be able to read the SOAP message for attachment content.  

The following links to articles provide more background to the issue:

https://visualstudiomagazine.com/Articles/2006/05/01/Implement-a-File-Transfer-Web-Service.aspx
....."At this time, binary data smaller than 768 bytes is base64 encoded and inserted into the SOAP message ...  Otherwise, MTOM uses MIME parts to send the data...."

https://www.google.com/search?safe=off&sxsrf=ACYBGNT3CEh0w5fb8z2fktIH3fjdbI0aAw:1578425791562&q=WCF+MTOM+attachment+mime+%22768%22&sa=X&ved=2ahUKEwil0PCknvLmAhWmq1kKHRGcCxQQ5t4CMAZ6BAgIEAk&biw=1920&bih=937

1 Comment
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
Status changed to: Waiting for Votes
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.