DO NOT REPLY [Bug 18024] - Bad client handling of HTTP 204 NO CONTENT response

[bu...@apache.org]

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





------- Additional Comments From andras.avar@nokia.com  2003-07-17 15:27 -------
A question about the ONE-WAY message handling in case of INVALID BEHAVIOUR. So, 
as far as we know the appropriate status code on successful transmission is 
"204". 

What if there is a PARSING ERROR - that hopefully brings up a lot of question - 
anyway how can we identify the operand and its type (one-way or bi-directional) 
? As we cannot determine the type we have to assume that the request was a 
bi-directional one and we should send back a soap fault (some kind of parsing 
details) with http status code "500". - but this means for a one-way invoker 
that the message transaction is not successful.

Shall we have to define something in the URI or on HTTP layer that can sign 
differences between the bi-directional and the one-way messages ? So, a solution 
can be to give a parameter to the request URI which can be handled by the 
AxisServlet to state that this is a one-way message and use it to set the 
response properly. Or a better one can be to add another service name (or port) 
to the original one in wsdd (like "something, something_oneway") to handle all 
the one-way operations through the second service.

The point is to make differences between the operands on transport level.

Any thoughts ?

Br,
Andras