LABEL method and Multi-Status

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

LABEL method and Multi-Status

Werner Donné

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.
--
Werner Donné  --  Re
Engelbeekstraat 8
B-3300 Tienen
tel: (+32) 486 425803 e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: LABEL method and Multi-Status

Manfred Baedke

Hi Werner,

if COPY failed for the resource identified by the request uri, it could
not be successful for any resource. This is not the case with LABEL.

Regards,
Manfred

Werner Donné 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.
>  

Reply | Threaded
Open this post in threaded view
|

Re: LABEL method and Multi-Status

Manfred Baedke
In reply to this post by Werner Donné

Of course, the requirement that

... 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 ...

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

Regards,
Manfred

Werner Donné 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.
>