httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grand Zorro-uin" ...@mh-freiburg.de>
Subject mod_dav and collection URIs (possible bug?)
Date Wed, 21 Nov 2007 22:23:36 GMT
Dear list,

I just observed a strange bug in mod_dav's provider interface: 
my custom provider callbacks need to use the resource->uri value to
store/retrieve properties from a custom property store. Unfortunately 
it seems as if the resource->uri for _collections_ isn't consistent 
at all (I'm (ab)using the file backend provider for storage so far).
Here's a printf style debugging output for several WebDAV calls for properties
on a collection resource:

[Wed Nov 21 22:56:32 2007] [warn] [URI in fcall to 'dav_cms_db_store' is
'/cms/c'] <------ Hic!
[Wed Nov 21 22:56:40 2007] [warn] [URI in fcall to 'dav_cms_db_output_value'
is '/cms/c/']
[Wed Nov 21 22:56:40 2007] [warn] [URI in fcall to
'dav_cms_db_define_namespaces' is '/cms/c/']
[Wed Nov 21 22:56:56 2007] [warn] [URI in fcall to
'dav_cms_db_define_namespaces' is '/cms/c/']
[Wed Nov 21 22:56:56 2007] [warn] [URI in fcall to 'dav_cms_db_first_name' is
'/cms/c/']

Note the missing '/' in the first callback - this is the result of calling
PROPATCH on
the resouce '/cms/c/'. Before I start diving into the code myself: any idea
what's going
wrong here?

TIA Ralf Mattes


--
R. Mattes 
Hochschule fuer Musik Freiburg
rm@inm.mh-freiburg.de


Mime
View raw message