[ http://issues.apache.org/jira/browse/JCR-165?page=comments#action_12320453 ]
Brian Moseley commented on JCR-165: ----------------------------------- section 8.4 of RFC 2518 says: "The semantics of GET are unchanged when applied to a collection, since GET is defined as, "retrieve whatever information (in the form of an entity) is identified by the Request-URI" [RFC2068]. GET when applied to a collection may return the contents of an "index.html" resource, a human-readable view of the contents of the collection, or something else altogether. Hence it is possible that the result of a GET on a collection will bear no correlation to the membership of the collection." so it's not that GETing a collection doesn't belong to webdav, but rather that the content of the response is undefined. you have to make *some* kind of response, even if you don't want to send a traditional html directory listing. however you ultimately choose to handle the issue, though, i don't have any problem handing it at the servlet level rather than in the export chain. > add ability to ignore specific node types when generating webdav directory > listing > ---------------------------------------------------------------------------------- > > Key: JCR-165 > URL: http://issues.apache.org/jira/browse/JCR-165 > Project: Jackrabbit > Type: Improvement > Versions: 1.0 > Reporter: Brian Moseley > Priority: Minor > Attachments: dirlisting.patch > > attached is a patch that enhances DirListingExportCommand to allow specific > node types to be ignored when generating the html directory listing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
