RE: Marshalling Depth > 0 responses for REPORTs, WAS: Replacing t he Label header with a DAV:labeled-version report

Sorry,

problem doesn't go away :-)

>    Related question of the day: what's the response format for the
>    version-tree report with depth: 1 applied to a collection that
>    itself is not versioned but contains one version controlled member?
>
>    For depth 0 I'd expect:
>    409 CONFLICT
>    with
>    <error xmlns="DAV:"><supported-report/></error>
>
> Sounds right.
>
>
>    So for depth 1 one would get:
>    207 MULTISTATUS
>    <multistatus xmlns="DAV:">
>      <response>
>        <href>/collection/</href>
>        <status>HTTP/1.1 409 Conflict</status>
>        <responsedescription><error><supported-report/>
>          </error></responsedescription> </response>
>      <response>
>        <href>/collection/a</href>
>        <propstat>
> 	 <prop>
> 	 ...now what?...
> 	 </prop>
> 	 <status>HTTP/1.1 200 OK</status>
>        </propstat>
>      </response>
>    </multistatus>
>
> Yes.


So,

assume we do a depth: infinity REPORT locate-by-history. This report is
defined for collections only, so it must return FORBIDDEN for all
non-collection resources it is applied to. This suggests that in the case of
depth: infinity, I will get a

<response>
    <href>...</href>
    <status>HTTP/1.1 403 Forbidden</status>

<responsedescription><error><supported-report/></error></responsedescription
> </response>
<response>

element for every single non-collection resource in the namespace below the
request URI. Is this really intended???

Julian