Replies: 1 comment
-
Created issue feature request #4471 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi. The preprocessor functionality is really interesting. But can it handle an HTTP binary upload? I get an 415
Unsupported Media Type when trying a binary upload with Postman.
curl --location 'http://domain.com/api/r/test?a=1&b=2' --header 'Content-Type: application/pdf' --data '@/temp/tm1.a.pdf'
I have a flow which processes a file and returns some data about the file. At the moment the flow takes base64 input. But I'd like to see if I can decrease the upload size by allowing a binary upload instead of having to use base64 text. The goal is also to improve the endpoint consumer's experience so they can use a tool like Postman or Curl without first needing to convert the file to base64.
Maybe the acceptable content-type could be set in the Custom HTTP route and it passes the raw body to the preprocessor.
Beta Was this translation helpful? Give feedback.
All reactions