Can't send attachments using soapUI 3.6 Pro
Using soapUI 3.5.1, an image attached to the request I'm sending in to my system was encoded into a long string, visible in the RAW output of the request, as such: POST http://qa01:8080/smartagent...
Forum Discussion
I am having the same issue. Created functional tests in soapUI Pro 3.0.1 that sends a request with an attachment that is on the file system. Works fine in soapUI pro 3.0.1. Recently upgraded to 3.6 build dist-109-2010-09-13, build date 2010/09/13 13:46. Now these files either are not getting attached or are corrupted as they got to the server properly. For example, I upload a word doc and when I try to view it (following an attempted soap request to place on the server) Word is unable to open it.
This is particularly a problem as I am hoping to use the soapUI to loadUI functionality and use loadUI to do performance tests.
When running the request, my Raw request header for 3.6 is:
Content-Length: 1103
For 3.0.1 it is:
Content-Length: 62530 (looks like there is no attachment included)
Further, in the 3.6 request there is nothing beyond the header in the request - i.e. no soap envelope. In 3.0.1 I see the whole request.
Did something change with 3.6? Is there something else that I need to do?
This is particularly a problem as I am hoping to use the soapUI to loadUI functionality and use loadUI to do performance tests.
When running the request, my Raw request header for 3.6 is:
Content-Length: 1103
For 3.0.1 it is:
Content-Length: 62530 (looks like there is no attachment included)
Further, in the 3.6 request there is nothing beyond the header in the request - i.e. no soap envelope. In 3.0.1 I see the whole request.
Did something change with 3.6? Is there something else that I need to do?