Re: [Bug 12] Destination header "consistent"

Julian Reschke <julian.reschke@gmx.de> wrote on 11/01/2005 04:33:00 AM:

> 
> So from what I can see here, the issue was about a server that was using 

> URLs in PROPFIND responses that weren't descendants of the Request-URI. 
> This is a server bug, and if RFC2518 needs to be clearer about this, I'm 

> +1 on doing that.

I agree.  If we do need to be clearer on this, we could add a sentence to
the following paragraph from section 8.1 (PROPFIND) of 2518:

"Consequently, the multistatus XML element for a collection resource with 
member URIs MUST
 include a response XML element for each member URI of the collection, to 
whatever depth was
 requested. Each response XML element MUST contain an href XML element 
that gives the URI of the
 resource on which the properties in the prop XML element are defined. 
Results for a PROPFIND on a
 collection resource with internal member URIs are returned as a flat list 
whose order of entries is not
 significant."

I'd be happy to add a sentence to the effect that:

"Note that the URI in the response XML element must consist of 
 the request-URI of the collection resource extended by a sequence
 of 0 or more slash separated pathname segments."

Cheers,
Geoff