DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18024>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18024 Bad client handling of HTTP 204 NO CONTENT response Summary: Bad client handling of HTTP 204 NO CONTENT response Product: Axis Version: current (nightly) Platform: PC OS/Version: Windows XP Status: NEW Severity: Minor Priority: Other Component: Basic Architecture AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] when somehow the server doesn�t generate any content, it goes if (responseMsg == null) { res.setStatus(HttpServletResponse.SC_NO_CONTENT); if(isDebug) log.debug("NO AXIS MESSAGE TO RETURN!"); But the client side doesn�t recognise this 204 fault code as anything other than success, and expects proper XML [java] org.xml.sax.SAXParseException: Premature end of file. [java] at org.apache.axis.AxisFault.makeFault(AxisFault.java:129) [java] at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:543) [java] at org.apache.axis.Message.getSOAPEnvelope(Message.java:377) [java] at org.apache.axis.client.Call.invokeEngine(Call.java:2545) [java] at org.apache.axis.client.Call.invoke(Call.java:2515) [java] at org.apache.axis.client.Call.invoke(Call.java:2210) [java] at org.apache.axis.client.Call.invoke(Call.java:2133) [java] at org.apache.axis.client.Call.invoke(Call.java:1656) Either the client sees 204 & handles it, or we return something else. Recommendation: what does the WS-Basic profile suggest? IF nothing, we should add it?
