Hi, Within the legacy system I am writing a WebDAV interface for, there is an object type which exhibits both properties of a collection (it can contain members) as well as a non-collection resource (it can have data associated with it). In the first instance I opted to make them look like non-collections, so a GET would return the data associated with them (rather than the html directory listing).
I thought that setting the recently added 'directory-browsing' flag to false would allow me to label them as collections and specify the data to return from a GET request. However, when I read a little deeper I saw that this will only cause a 403 to be returned. Is it feasible or indeed valid to support this type of object? Any information or pointers anyone can give me would be appreciated. Thanks ...Col
