Empty response gives empty XML, Xpath parsing fails
I've noticed this behavior between different servers.
When accessing directly to the Tomcat server, SoapUI works fine. When I get a 204 response for a REST request, I get this response in the XML tab :
But when I change the URL of the server to hit the Apache server, who is load balancing over many Tomcat servers, when I get a 204 response the XML tab is empty.
This causes my XPath requests to fail (the conditional goto won't even do anything because of "missing content from previous test request", and is skipped from my test cases for example).
I've noticed the headers have changed according to which server I use.
With the tomcat, I have the following headers in the response : Server and Date.
With the Apache, I have the following headers in the response : Server, Data, Content-Length: 0, Vary (Accept-Encoding, User-Agent), Content-type (application/xml), X-Cache, Via, Proxy-Connection (keep-alive).
Any idea ?
Thank you
When accessing directly to the Tomcat server, SoapUI works fine. When I get a 204 response for a REST request, I get this response in the XML tab :
<data contentType="text/plain" contentLength="0"><![CDATA[]]></data>
But when I change the URL of the server to hit the Apache server, who is load balancing over many Tomcat servers, when I get a 204 response the XML tab is empty.
This causes my XPath requests to fail (the conditional goto won't even do anything because of "missing content from previous test request", and is skipped from my test cases for example).
I've noticed the headers have changed according to which server I use.
With the tomcat, I have the following headers in the response : Server and Date.
With the Apache, I have the following headers in the response : Server, Data, Content-Length: 0, Vary (Accept-Encoding, User-Agent), Content-type (application/xml), X-Cache, Via, Proxy-Connection (keep-alive).
Any idea ?
Thank you