Contributions
Re: Multipart requests to a mock service under SSL appear to be truncated
Did you find any solution? I have the same problem. Our application sends request with MTOM attachment to SaopUI. Attachment in SoapUI is all right when SSL is not used. If SSL is enabled, received file hasno more than 6882 B (even if the original file was bigger). I implemented my own mock service and there was no problem with bigger files. So, the problem should be connected with SoapUI (its configuration or something else) but I do not know what is wrong.1.1KViews0likes1CommentFile size for attachment received via HTTP request
We use SoapUI for testing of Web Services. It acts as a mock service. Our application sends requests with MTOM attachment. If this attachment is smaller than 6882 B, everything is all right. If it is bigger only a part of it is received by SoapUI - in attachment tab (of Message Viewer in SoapUI) is size 6882 B and when it is exported to the file, it is broken (file is not complete). I tried to send a request through HTTP (instead of HTTPS). I disabled SSL for transport layer on both our application and SoapUI. Then the received attachment was all right (even if it was bigger than 6882 B). Is there some file size limit or configuration for https requests which can be received by SoapUI? Has anybody an experience in sending of XOP (MTOM) attachment which is bigger than 6882 B to SoapUI?954Views0likes0Comments