This turned out to be an interesting issue…
I had loglevels for REST Consume set to trace the entire time I was testing this rest call. Ended up closing my modeler and then opening it again the next day and the call worked!
Determined to figure out what had been causing my issue, I set loglevels for REST Consume back to trace. All of a sudden, the Rest response images start coming in corrupted again.
Turns out it was the Trace itself that was corrupting the contents of the incoming Binary file! Definitely makes me appreciate why base64 encoded images are standard for REST services
Hey,
Could you check in Console with “REST Consume” log level set up as Trace what you are receiving from your endpoint? There is a slight chance that Postman is adding some header value which Mendix does not (I had something similar in my project, had to stop and start local app after changes as Rerun locally didn’t reflected all changes what I made to REST call)
If response is exactly same then you may check what returns ‘StringFromFile’ from CommunityCommons (if you are sending/receiving file)
It is worth to check how it works on your computer and after deployment – database encoding may play a role there