[Registered] HTTP Post in SOAPUI
Hey guys, I apologise in advance if this is overly convoluted and ambiguous but I will attempt to be as precise and clear as I can. I have a TestCase setup in my SOAPUI project with the follow elem...
Forum Discussion
Our Server is Windows 2003 running Cold Fusion 10
For test purposes I have created a simple cold fusion test page (testpage.cfm) that will accept a HTTP post containing a parameter called “download_reference”.
We can successfully post to this page from my web browser using a form (index1.htm) however when I post to the same page using SOAP UI we receive Server Error 500 in the response.
After comparing the contents of a working HTTP post vs the one generated by the SOAP UI tool, I can see that there is an unwanted extra line included in the HTTP request generated but SOAP UI tool as indicated by the arrow in the network trace below.
SOAP UI Generated POST
Working HTTP POST
Using the same HTTP Post body as above but with the additional Line removed and Content-Length Adjusted accordingly I received 200 OK back from my server.
This looks like it may be a bug in the SOAP UI tool although some Web Servers handle this better than others. Any chance this might get fixed in the SOAP UI Tool any time soon? Or suggestions on workarounds?
For test purposes I have created a simple cold fusion test page (testpage.cfm) that will accept a HTTP post containing a parameter called “download_reference”.
We can successfully post to this page from my web browser using a form (index1.htm) however when I post to the same page using SOAP UI we receive Server Error 500 in the response.
After comparing the contents of a working HTTP post vs the one generated by the SOAP UI tool, I can see that there is an unwanted extra line included in the HTTP request generated but SOAP UI tool as indicated by the arrow in the network trace below.
SOAP UI Generated POST
Working HTTP POST
Using the same HTTP Post body as above but with the additional Line removed and Content-Length Adjusted accordingly I received 200 OK back from my server.
This looks like it may be a bug in the SOAP UI tool although some Web Servers handle this better than others. Any chance this might get fixed in the SOAP UI Tool any time soon? Or suggestions on workarounds?
