I hope it is okay to re-open this old thread. My team (I am just the Scrum Master trying to solve an impediment) works with soapUI, testing RESTful (not SOAP!) web services functionally.
We have several POST requests containing attachments (images and other binaries). Because we quote failed tests in our Jenkins reports (sent via e-mail) it is quite impractical that the transfer encoding is always "binary". We would like to use "base64" - not just for the sake of clean e-mails, but for other reasons too. Has soapUI evolved to a state in which this is possible (preferrably configurable via the UI as a property of the attachment or the whole request)? We tried adding a "Content-Transfer-Encoding: base64" HTTP header, but to no avail. -- View this message in context: http://cxf.547215.n5.nabble.com/Setting-soap-attachment-Content-Transfer-Encoding-tp3335835p5722843.html Sent from the cxf-user mailing list archive at Nabble.com.
