Hey Killian tnkz for your time. 

In Outsystems I expose a RestApi with a input inputParameter Binary Data. I recieve the XML in the body. The XML is send by the client in 2 ways:

1. The client sends from postman a binary file, 
2. The client sends the XML as a multipart/form data

The first way, works fine. De binary file is saved to a record. And on create of that record, the XML is procecced by Outsystems trough use of the XML extensions of Outsystems, see third screenshot.

The second way does not work, The xml file contains also the disposition data from the headers, see please my second screenshot. And so processing  of the XML fails.

I want to know, is there a way to send a multipart request that does not put the disposition data inside of the binary file ?

I hope this give you more info

Hi Marz,

I think you completely misunderstand how things work at a low level when exposing a REST API. When you expose a REST API that has a single parameter of type Binary Data, that is received in the body, you basically tell OutSystems that everything you are going to receive is structureless Binary Data. Everything sent as body in the request from an external source will be treated as one blob of data. It's totally up to your interpretation what that is going to be. There is absolutely no way¹ for OutSystems to know that there are two ways the data is going to be sent. In fact, it is breaking any sane convention of exposing/calling a REST API method, as you basically have the same method being called with totally different sets of data!

So your question "is there a way to send a multipart request that does not put the disposition data inside of the binary file" is totally misinformed. What the client sends you is a well-formed multipart/form-data request, which means there's a header, followed by binary data. In that header may be some indication you are dealing with a file. But since you expect a blob of binary data, everything the client sends is treated as structureless binary data. So the "disposition data" isn't "inside of the binary file", it is part of the payload that's sent to you, which includes both the header ("disposition data") and the file content.

Now, to resolve this mess you can do two things:

1. Create two seperate methods, one for receiving a binary blob that you treat as an XML file, one for the multipart/form-data. The latter you can then process using the Multipart/form-data Forge asset.
2. Accept that you may receive two very different types of data. Check the Content-Type header to see if it contains "multipart/form-data", and if so use the Multipart/form-data asset to process it, or do it "manually" like Matheus suggested.

I'd go for option 1, but it may be easier to use option 2.

¹Well, it could theoretically check the Content-Type header, assuming that the client sets it appropriately. But OutSystems doesn't have native handling of incoming multipart/form-data, so it wouldn't matter.

Tnkz Killian for explaining this in detail. I will look into both suggested solutions.

Appreciate greatly your help with this

Sure, np, glad I could be of help :).