You might have a misunderstanding in how your endpoint expects to receive its data - double check the spec.
If you are to send a file as an attachment (multipart) as you are doing already, then your endpoint should be able to manage all of those Content-Transfer-Encodings, as these are well specified and I can't imagine endpoint developer is not using a standard library.
Which is why I suspect they are expecting it in another way? Perhaps as a single request body, perhaps in a header, perhaps embedded into JSON? In these cases you would do the base64 encoding yourself (groovy-lang.org) and specify the data wherever it really belongs.
Thanks for your reply JHunt.
What do you mean by "If I send a file as an attachment (multipart)" ?
I don't use soapUI's attachment functionnality to make my POST request. But I send my file throw a request parameter (name "content") encoded in Base64 (as required our spec).
I just want to know if it is possible to avoid soapUI such raw (multiple return lines and adding some characters at the end of each of them). I believe that it was related to "Content-Transfer-Encoding:quoted-printable" setting made by soapUI.
Below my service settings with details of base64 request parameter
If my zip file parameter encoded in based64 doesn't contains any pdf file, i don't why (may be due to the parameter length), but soapUI manage it correctly en the parameter Content-Transfert-Encoding : 7bit (see bellow)
How to get the same if my zip file contains pdf file ?
PS: To encode in base64 my zip file, i follow your site exemple (see bellow).
I install ReadyAPI solution, the same request execute properly 🤔
