HTTPClient vs SOAPUI.
Hi,
I wonder if anyone who has worked on SOAPUI source might be able to provide some insight on this StackOverflow thread:
http://stackoverflow.com/questions/14754623/post-using-soapui-works-manual-java-client-using-apache-httpcomponents-httpclie
Essentially it boils down to the fact that making a POST request to a particular https resource using SOAPUI works as completely as expected and the server returns a 200 status. Whereas making a POST request to the same resource using Apache HttpClient doesn't work as expected and the server returns a 400 status along with a "Bad Request" message.
Also for that matter, using a standard HttpsURLConnection also returns a 400 status.
I'm guessing SOAPUI is doing something under the covers which means that the request is slightly different when it hits the server but I can't figure out what that might be.
Any advice would be very appreciated.
Cheers,
Lee
I wonder if anyone who has worked on SOAPUI source might be able to provide some insight on this StackOverflow thread:
http://stackoverflow.com/questions/14754623/post-using-soapui-works-manual-java-client-using-apache-httpcomponents-httpclie
Essentially it boils down to the fact that making a POST request to a particular https resource using SOAPUI works as completely as expected and the server returns a 200 status. Whereas making a POST request to the same resource using Apache HttpClient doesn't work as expected and the server returns a 400 status along with a "Bad Request" message.
Also for that matter, using a standard HttpsURLConnection also returns a 400 status.
I'm guessing SOAPUI is doing something under the covers which means that the request is slightly different when it hits the server but I can't figure out what that might be.
Any advice would be very appreciated.
Cheers,
Lee
