Thanks for you different feedbacks. But unfortunately, these do not help me to fix my issue.
I just want to know why I have two different results with the same script execution (soapUI vs ReadyAPI).
My request has two parameters "filename" and "content". The second parameter is filled by a very long string (the result of zip file encoded in Base64).
As I can see, with soapUI, "content" parameter has quoted-printable "Content-Transfer-Encoding" value. Is there any way to avoid this setting done by soapUI ?
With ReadyAPI, the same request editor is different, "content" parameter has no "Content-Transfer-Encoding" value (in Request Raw view there is no break line).
As I said below, it depends of content length.
Under a specific value soapUI keep Content-Transfer-Encoding value to 7bit
Over a specific value soapUI seems to format the content value as Content-Transfer-Encoding set to "quoted-printable" value. It seems that soapUI edit the request as we can see (on request raw) multiple break lines.
