Different WebDav resource paths for same resource when using different clients...
I am in the process of testing a web dav enabled view my system using anumber of different clients. One particular client seems to do sometimes do strange things and I was wonder is this to be expected.. The log below shows how it has somehow mangled the path to the directory(collection in webdav speak) by including again the full path ...