> 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).
Slide has no problem with this (collection + data), but WebDAV does. Although it's not strictly forbidden (collection are allowed to return whatever they want in response to a GET), none of the available clients will display the content. > 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. Yes. I think it would make sense to change that to: if there's content, display it, instead of displaying a directory browsing page (similar to how welcome pages behave). Remy
