Forum Discussion

kriegaex's avatar
kriegaex
New Contributor
12 years ago

Change transfer encoding of attachments to base64

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", because this leads to binary content being inlined into our e-mails. We would like to use "base64" - not just for the sake of clean e-mails, but for other reasons too. Is this 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.

2 Replies

Sort By
  • kriegaex's avatar
    kriegaex
    New Contributor
    12 years ago
    Ping! Anybody here who can answer this question? Thank you very much.
  • Abneo's avatar
    Abneo
    10 years ago
    Having an attached way of moving ahead in a particular format that surely have an impact with overall ways and at the end it can surely let you move ahead and this is the way how it normally helps and because scrum is simply good at growth the outcome can be reasonable.