RE: Issue: describing the HTTP error text for faults

Thank you for the comment below, and for your patience with us in
resolving it.  We tracked the comment below as Issue LC47 [1].  The WG
agreed to add a reasonPhrase attribute as outlined in [2].  The fix
should be in the latest editor's draft at [3].

If you agree with our disposition of your comment, we'd like you to
acknowledge it within two weeks; otherwise we will assume you are
satisfied.  The WG plans to enter a second (short) Last Call period in
the near future, and we invite you to review that publication as well.

[1] http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC47
[2] http://lists.w3.org/Archives/Public/www-ws-desc/2005Apr/0007.html
[3]
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20-adjuncts.
html

> -----Original Message-----
> From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org]
> On Behalf Of Roberto Chinnici
> Sent: Wednesday, September 15, 2004 1:18 PM
> To: www-ws-desc@w3.org
> Subject: Issue: describing the HTTP error text for faults
> 
> 
> As discussed at the f2f, when binding a fault to the HTTP protocol,
> we need to be able to specify the error text in addition to the HTTP
> status code. The rationale is that the client may want to use
> the error text to distinguish between faults with the same status
> code.
> 
> Roberto

Received on Tuesday, 3 May 2005 20:16:52 UTC