What is your goal?A working HTTP Request module with raw request now that it was changed by Make.
What is the problem & what have you tried?Make changed the HTTP Request module for some strange reason. Removed the Body content type that allows Raw and offers no alternative. Before my scenarios worked fine specifying Raw, Content type as Custom and then value as application/pdf. And of course it no longer works correctly.
Screenshots (scenario flow, module settings, errors)I should mention, if you review my other posts regarding custom module, this is exact same type of error receiving over there. The binary is not valid even though i am certain the file is valid and works in Postman, curl, etc.
Hey James,
contact Make support directly about this.
I thought setting the Body Content Type to Custom now would be the equivalent to what Raw was before.
I’ll test some scenarios tomorrow morning to see what other differences might popup.
I got a pretty cursory answer by someone that doesn’t appear fully versed on HTTP or development. Their “fix” was for me to change to multipart/form-data. Of course, the endpoint is published endpoint and I can’t just change it. The endpoint takes raw binary of content type application/pdf. It worked before in the old Http Module, now it doesn’t. The bug is it is that the module is setting the type to text, not I’m setting the type to text lol. Hope someone at Make.com reads the forums as based on the response I got, I doubt that person will be able to help me or escalate it to appropriate channels.
Hopefully someone does read this, as the issue is also happening when trying to create a custom component. Make.com insists on turning the binary data into a string.
Hi James,
Greetings! I hope you’re doing well.
Thank you for reaching out to us. This is Suryansh from the Customer Care team, and I’ll be happy to assist you with your issue today.
I saw your scenario in the HTTP “Make a Request” module and noticed that in the Body Content field, the data type is set to Text, while you are passing Buffer data. This mismatch is causing the error.
Oh they will be able to escalate, just keep pushing.
Make employees do check the forums but you will get a faster response via mail.
Support confirmed this is a bug.
