Re: another approach to status codes, etc. in HTTP binding

Oops, hit send prematurely.  I'll just respond to the one point I missed.

7/19/2001 3:20:30 AM, christopher ferris <chris.ferris@east.sun.com> wrote:

>Mark,
>
>Okay, if we take this approach (reuse application semantics)
>to its fullest interpretation, then yes, SOAP Server.* faults
>would be reported using 500 and possibly MustUnderstand.*
>faults (of course, depending upon your perspective, either
>the client is at fault for including a header that the server
>doesn't understand or the server is at fault for not understanding
>the header;-).

Yah, I got a headache over this one at first too until I looked at the Expect feature of HTTP 1.1.  Then all was made 
clear; it is within the capabilities of the client to resubmit the request without mustUnderstand="1".  The server doesn't 
have a choice.

MB