* Chris Knight wrote:...
So, Catacomb and other mod_dav backends that handle GET requests would like to have the Content-Type of resources be automatically identified based on the path information of that resource in the same manner as file resources.
ModMimeUsePathInfo was created for this purpose IIRC.
Indeed. The only caveat is that ModMimeUsePathInfo shouldn't necessarily be enabled on resources that you edit. The problem comes into play when filters are applied and the transmitted representation differs from the on-disk (in-storage) resource. (This is actually a major collision with REST that WebDAV never quite solved cleanly - it just assumes that the resource == representation.)
The best example is with mod_include'd files. With ModMimeUsePathInfo On, there is no way to disable the output filters when communicating with a DAV client. Therefore, the solution is to mount the repository twice - once as read-only with ModMimeUsePathInfo On and another one with it Off so that the DAV clients can modify without having the filters executed and get the 'raw' representation.
Hope that makes sense. If not, I can try to clarify. -- justin
