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 [EMAIL PROTECTED] 2003-03-26 12:32 ------- Hi Steve, In the HTTP/1.1 (RFC 2616) definition, the message styles of the payload are specified as follows; +----------------------------+ |[Request-Line | Status-Line]| <- [HTTP protocol headers] | (message-header CRLF) | +----------------------------+ CRLF +----------------------------+ | message-body(entity-body) | <- [HTTP protocol massage] +----------------------------+ In addition, the 2xx series of status codes indicate the 'successful' state, '204 No Content' means the payload doesn't have a message-body. In other words, 'HTTP massage' is NULL. By applying the same logic to SOAP over HTTP, you may reach a conclusion which a SOAP response should be allowed to omit the message-body from the payload of HTTP with the status code of '204 (No Content)'. On the other hand, WS-I Basic Profile Version 1.0 said; <http://www.ws-i.org/Profiles/Basic/2003-01/BasicProfile-1.0-WGAD.html> [2xx series of status codes] | HTTP uses the 2xx series of status codes to communicate success. | In particular, 200 is the default for successful messages, but | 202 can be used to indicate that a messages has been submitted | for processing. Additionally, other 2xx status codes may be | appropriate, depending on the nature of the HTTP interaction. [202 Accepted] |R1112 | An INSTANCE SHOULD use either a "200 OK" or "202 Accepted" HTTP | status code for responses that indicate successful HTTP outcome of | a request but do not contain a SOAP message. The important things are three sentences; - Additionally, other 2xx status codes may be appropriate, depending on the nature of the HTTP interaction. [Comment] --> So, we can use '204 (No Content)'. - An INSTANCE SHOULD use either a "200 OK" or "202 Accepted" HTTP status code for responses that indicate successful HTTP outcome of a request but do not contain a SOAP message. [Comment] --> The code of "202 Accepted" in the basic profile is equal to "204 No Content" of the HTTP/1.1 spec. - Despite the fact that the HTTP 1.1 assigns different meanings to response status codes "200" and "202", in the context of the Profile they should be considered equivalent by the initiator of the request. [Comment] --> There's a mismatch on two specs (RFC & WS-I profile). [for reference, HTTP/1.1] | The 202 response is intentionally non-committal. Its purpose is to | allow a server to accept a request for some other process (perhaps a | batch-oriented process that is only run once per day) without | requiring that the user agent's connection to the server persist | until the process is completed. The entity returned with this | response SHOULD include an indication of the request's current status | and either a pointer to a status monitor or some estimate of when the | user can expect the request to be fulfilled. I'm not sure why WS-I doesn't use the code of '204 No Content' to indicate the true meaning of "No content", because I don't have a detailed review on it. Best Regards, Toshi (Toshiyuki Kimura) <[EMAIL PROTECTED]> R&D Headquarters NTT DATA Corporation
