RE: BIND Error Codes

Adding yet another error code for this is probably a waste. I think 501 is
the right code but you should add an XML body with an element indicating
what went wrong. You could use a header but the error status is something
(as you are now finding) that people will want to be able to expand in the
future. XML is expandable, headers are not.

		Yaron

> -----Original Message-----
> From: Slein, Judith A [mailto:JSlein@crt.xerox.com]
> Sent: Wed, September 15, 1999 11:19 AM
> To: 'WebDAV'
> Subject: BIND Error Codes
> 
> 
> Another in the series of messages from the advanced 
> collections design team:
> 
> We've agreed to remove all normative language about 
> cross-server bindings,
> but we do think it would be useful to say something about the 
> reason why a
> binding cannot be created, especially in the case of an 
> attempt to create a
> cross-server binding.
> 
> We haven't been able to agree on how best to do this.
> 
> Currently the binding spec says that if the server can't guarantee the
> required binding behavior, it must fail the BIND request with 
> a 501 (Not
> Implemented).  Period.  No further explanation.  We could 
> just leave it at
> that, but we think it would be useful to the client to know 
> that the reason
> the BIND can't be done is that the server can't guarantee integrity of
> bindings to resources on another server (for example).
> 
> We could use a different (new) error code for "Can't create 
> cross-server
> binding."
> 
> We could stick with 501, but provide further explanation in 
> the response
> body.
> 
> We could leave the spec as it is.
> 
> Any preferences?
> 
> --Judy
> 
> Judith A. Slein
> Xerox Corporation
> jslein@crt.xerox.com
> (716)422-5169
> 800 Phillips Road 105/50C
> Webster, NY 14580
>

Received on Wednesday, 15 September 1999 19:53:47 UTC