multipart/form-data w/ boundaries - request failing - same headers/body pass using fiddler
This is my first post, first impassable issue I have run into with soap ng so far. I am testing a batch upload service for work and I have used fiddler for a sanity check before trying to create a regression suite for the service with soap ng. The sanity check through fiddler works fine, but the exact same test throughsoap ng is failing. The only difference between the two that I can see is the content-length is larger with soap ng. The content-length for this service is important and the request through fiddler will fail if it is not correct. I have tried to manually specify the content-length insoap ng but the request instantly fails when I do this, it looks like it doesn't even try to connect to the endpoint at all. I get back "<missing raw response data>" when manually specifying the content-length. At this point I am thinking the content-length is the culprit. I will post screenshots of the two applicatons with the tests loaded. If anyone has experience using multipart content types with boundaries and soap ng, please advise how you have gotten your tests to work. The fiddler setup is working, I copied that as close as possible tosoap ng which is failing. fiddler content-length = 616 soap ng content-length = 757 (where is the extra length coming from?) SOAP NG REQUEST FIDDLER REQUESTRequest Content-Length was not available in raw request
Note: The Test is working fine with different environment Given Specific environment When Request made Then noContent-Length was generated by soap UI pro in Raw tab And Request Log contains error : 2018-07-04 22:47:50.123 - Error getting response; java.net.SocketException: Software caused connection abort: recv failed FYR: But the same endpoint is working fine in different project under Soap UI Pro for the same environment and the different between this projects are the Content-type headers are passed from Request - Header tab in case of working project and for not working projectContent-type headers are passed from Request tab directly FYR: Challenging things are the same suite working in different environment and the same endpoint working in different project for the same step Please support on sharing the area i should check to identify the challenge ReadyAPI 2.4.0
