RE: Status code for creating lock-null resource

> Agreed on all of Jims points. I like the point about "URL is not
> mapped to a resource". Maybe it could be included in the revised RFC as it
> could make things clearer for some people ?

This sounds quite reasonable to me. I've added an issue about this to the
issues list.

> IMHO, null resources have no properties. After all, they don't map to any
> resource within the server, can't do a PROPFIND on them etc. Is my
> interpretation wrong ?

No, your interpretation is correct. An unmapped URL does not respond to
PROPFIND requests.

> Just a reminder, LNRs have *all* the mandatory DAV properties
> (RFC 2518 sec 7.4), though as spec states, most will have no value (except
lock
> properties). One can legitimately perform a PROPFIND on a LNR and
> retrieve a DAV:* property.

Yes.

- Jim