Hi All,

I have been using Cadaver as a webdav client for quite a while now. In every 
projects so far I had to deal with a Hippo Repository. Cadaver proofed to be 
very useful. There has been only one limitation which is that the namespace of 
a property cannot be retrieved. You can set it, but obtaining the namespace of 
(existing) properties can not be accomplished.

My work around was to sniff the tcp traffic between the repo and the client to 
find out the namespaces that do cross the line when you issue a propget from 
Cadaver. This became a bit frustrating so I ended up posting on the Cadaver 
mailing list for a fix.

I recieved a patch from Henrik Holst of witsbits that will show the namespace 
when you issue a propget. This patch is attached for anyone interested. 

He also wrote that the Cadaver propnames command returned all the properties 
(including namespace) and not just the properties with the DAV: namespace.

According to RFC 2518 "HTTP Extensions for Distributing Authoring -- WEBDAV" 
this should indeed be the case (http://www.ietf.org/rfc/rfc2518.txt). See 
section 8.1.3 of the RFC for an example. However when I issue a propnames from 
Cadaver I only receive the properties with the namespace DAV: whereas there are 
also properties with the hippo namespace. This could lead to the conclusion 
that the server end does not return a specification compliant response.

When this is confirmed as being a bug I'll create a Jira issue for it (unless 
someone else has beaten me to it ;))


I'm using version 1.2.15 of the repository btw.

Regards,
Æde




_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/********************************************
Hippocms-dev: Hippo CMS development public mailinglist

Searchable archives can be found at:
MarkMail: http://hippocms-dev.markmail.org
Nabble: http://www.nabble.com/Hippo-CMS-f26633.html

Reply via email to