cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <dk...@apache.org>
Subject Re: Setting soap attachment Content-Transfer-Encoding
Date Thu, 07 Feb 2013 17:15:51 GMT

On Feb 7, 2013, at 5:07 AM, kriegaex <alexander@kriegisch.name> wrote:

> 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.

No idea on SoapUI.  You'd have to ask them.

I don't think we done anything on the CXF side to support this either.  Patches would be welcome.


-- 
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com


Mime
View raw message