Forum Discussion
SmartBear_Suppo
Alumni
12 years agoHi,
What I see from your http log is that at the end of the request SoapUI is appending unix line ending "\n" and apparently it seems mvc 4 parser has a bug (http://aspnetwebstack.codeplex.com/discussions/354215) that it crashes if it does not receive windows line ending "\r\n" at the end of the request.
Regardless of that, I have tried to send some request with multi-part form data and SoapUI seems to always send the windows line ending "\r\n". So, I was wondering it is possible to share some kind of sample project with sample attachment too so that we can reproduce the problem at our end. As long as we can see from http log that, it is not sending "\r\n" at the end of the request in that case we can further investigate this to figure out any solution or work around.
Regards,
Shadid
SmartBear Sweden
What I see from your http log is that at the end of the request SoapUI is appending unix line ending "\n" and apparently it seems mvc 4 parser has a bug (http://aspnetwebstack.codeplex.com/discussions/354215) that it crashes if it does not receive windows line ending "\r\n" at the end of the request.
Regardless of that, I have tried to send some request with multi-part form data and SoapUI seems to always send the windows line ending "\r\n". So, I was wondering it is possible to share some kind of sample project with sample attachment too so that we can reproduce the problem at our end. As long as we can see from http log that, it is not sending "\r\n" at the end of the request in that case we can further investigate this to figure out any solution or work around.
Regards,
Shadid
SmartBear Sweden