axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 18024] - Bad client handling of HTTP 204 NO CONTENT response
Date Thu, 27 Mar 2003 14:28:57 GMT
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 kimuratsy@nttdata.co.jp  2003-03-27 14:28 -------
Hi Steve,

  I agree with you and the soapbuilders discussion, so let's 
move to the next stage.  At first, I'd like to propose the
basic design to comply with the spec of HTTP/1.1 and JAX-RPC.

[Definition of the 2xx series of status codes, 200,202,and 204]
  - The 200 indicates the reponse including the results.
  - The 202 indicates that the request has been accepted,
    and the response includes 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.
    (The HTTP payload should include some contents.)
  - The 204 indicates the true meaning of 'No content'.
    (The HTTP payload should not have a message-body.)

[Table of the status codes according with the usages]
.........*.........*.........*.........*.........*.........*.........*
+----+-----------------+--------------+---------------+---------------+
| ID | Method types of | Server-Side  | Retrun val. of|Acceptable code|
|    | invoking        | Handlers     | the end-point |of HTTP/1.1    |
+====+=================+==============+===============+===============+
|  1 | invoke          | NONE         | ANY           | 200/ - / -    |
+----+-----------------+--------------+---------------+---------------+
|  2 | invoke          | NONE         | VOID          | 200/ - /204   |
+----+-----------------+--------------+---------------+---------------+
|  3 | invoke          | EXISTS       | ANY           | 200/ - / -    |
+----+-----------------+--------------+---------------+---------------+
|  4 | invoke          | EXISTS       | VOID          | 200/ - / -    |
|    |                 |(Adding some  |               |               |
|    |                 | SOAP Headers)|               |               |
+----+-----------------+--------------+---------------+---------------+
|  5 | invoke          | EXISTS       | VOID          | 200/ - /204   |
|    |                 |(NO Header)   |               |               |
+----+-----------------+--------------+---------------+---------------+
|  6 | invokeOneWay    | NONE         | ANY           | 200/202/ -    |
+----+-----------------+--------------+---------------+---------------+
|  7 | invokeOneWay    | NONE         | VOID          | 200/ - /204   |
+----+-----------------+--------------+---------------+---------------+
|  8 | invokeOneWay    | EXISTS       | ANY           | 200/202/ -    |
+----+-----------------+--------------+---------------+---------------+
|  9 | invokeOneWay    | EXISTS       | VOID          | 200/202/ -    |
|    |                 |(output a msg)|               |               |
+----+-----------------+--------------+---------------+---------------+
| 10 | invokeOneWay    | EXISTS       | VOID          | 200/ - /204   |
|    |                 |(no msg)      |               |               |
+----+-----------------+--------------+---------------+---------------+

  The above is the early draft of the proposal, so it might have some
error in writing.

Best Regards,

  Toshi (Toshiyuki Kimura) <kimuratsy@nttdata.co.jp>
  R&D Headquarters
  NTT DATA Corporation

Mime
View raw message