Re: LABEL method and Multi-Status

Of course, the requirement that

... If a Depth header is included and the request fails on any resource,=20
the response MUST be a 207 Multi-Status that identifies all resources=20
for which the request has failed ...

does not mean that the request could not fail with, for instance, 403 or=20
405 or whatever. Maybe this section could be reworded a little if there=20
will ever be a spec revision.

Regards,
Manfred

Werner Donn=E9 wrote:
> Hi,
>
> For the LABEL method RFC 3253 says:
>
> "If a Depth header is included and the request fails
> on any resource, the response MUST be a 207 Multi-Status
> that identifies all resources for which the request has
> failed."
>
> For the COPY method RFC 2518 says:
>
> "If an error in executing the COPY method occurs with a
> resource other than the resource identified in the
> Request-URI then the response MUST be a 207 (Multi-Status)."
>
> This seems to be inconsistent. Contrary to the LABEL method,
> the COPY would not return a Multi-Status if the Request-URI
> is the only one with an error or when the Depth header is "0",
> in which case there can't be another resource with an error.
>
> Regards,
>
> Werner.
>  =20