RE: Issues PUT_AND_INTERMEDIATE_COLLECTIONS and INTEROP_DELETE_AND_MULTISTATUS

But then, HTTP does not define the concept of collections and deep deletes.
WebDAV is an extension of HTTP, so when it introduces these new concepts,
isn't it allowed also to define error handling for it?

Yes, there's an issue with using a 2xx status for errors, but it doesn't
seem to have negatively affected any existing client I'm aware of.
RFC2518bis is supposed to clarify RFC2518, not to reinvent it.

Julian

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

> -----Original Message-----
> From: w3c-dist-auth-request@w3.org
> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Roy T. Fielding
> Sent: Wednesday, January 22, 2003 8:48 AM
> To: Lisa Dusseault
> Cc: 'Webdav WG'
> Subject: Re: Issues PUT_AND_INTERMEDIATE_COLLECTIONS and
> INTEROP_DELETE_AND_MULTISTATUS
>
>
>
> > Issue INTEROP_DELETE_AND_MULTISTATUS: this issue is a request for
> > DELETE errors to be 4xx so that HTTP clients don’t think 207 is a
> > success. That’s no longer really an issue – few HTTP clients do
> > authoring, and those that do are at least aware that 207 is a
> > multistatus response and not a complete success. We should resolve
> > this won’t fix.
>
> Doing that violates the HTTP protocol, not WebDAV.
>
> ....Roy
>

Received on Wednesday, 22 January 2003 10:39:54 UTC