Forum Discussion
The safest way to deal with multipart request is to use the attachment option in SoapUI. We can help with appropriate solution if you share a sample request the AWS is expecting.
Thanks,
Kondasamy
- subra79789 years agoOccasional Contributor
Thanks for the reply. In the screenshot above, one can see the raw multipart request from Soapui that has inserted a header for the attachment. I then downloaded the uploaded file from AWS S3 and a file "diff" with the original image shows the header has been included in the file content. So I gather AWS does not expect this multipart header. It counts everything after the message header as payload.
- nmrao9 years agoChampion Level 3Looks like you have different file encoding.
Can you please check this below link and see if that helps.
http://stackoverflow.com/questions/39222122/soapui-auth-header-with-special-characters/39244396#39244396- subra79789 years agoOccasional Contributor
This did not work. Either I should be able to disable multipart attachments, or if the solution is to include the file as binary payload, prevent HTML encoding of the payload.
Related Content
- 3 years ago
Recent Discussions
- 15 years ago