Here, this is taken from our SOAPMessageImpl.java:
* We are lazily encoding our message, which means that currently
* Content-Length is not being calculated. This should not be a problem
* because HTTP/1.1 does not require that it be sent (WS Basic Profile 1.1
* states that implementations SHOULD send HTTP 1.1). If it is determined
* that it must be sent, this perhaps should be done by the transport
* layer. However, there could be a space optimization where length is
* precalulated per attachment, and that calculation would, of course,
* belong here.
I don't consider it to be a bug. What issue's do you have with it? What client consumes that service?
Thank you very much for the response.
I am using the GSOAP C/C++ lib for the implementation of the client.
The GSOAP lib consider an HTTP 500 response without content as a failure and not as a SOAP FAULT.
And the library use the header Content-Length to know if the response is empty or not.