I'm trying to query sogo to using webdav and lockdiscovery at the address http://192.168.1.26/SOGo/dav/sogo1/Contacts/personal/ (where a lock exists on the collection).
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <D:propfind xmlns:D="DAV:"> <D:prop><D:lockdiscovery/> </D:prop> </D:propfind>" The response does not show any lock: <?xml version="1.0" encoding="UTF-8"?> <D:multistatus xmlns:D="DAV:"> <D:response> <D:href>/SOGo/dav/sogo1/Contacts/personal/</D:href> <D:propstat> <D:status>HTTP/1.1 200 OK</D:status> <D:prop /> </D:propstat> <D:propstat> <D:status>HTTP/1.1 404 Not Found</D:status> <D:prop> <D:lockdiscovery /> </D:prop> </D:propstat> </D:response> <D:response> <D:href>/SOGo/dav/sogo1/Contacts/personal/96D-5005BD80-1-60F2D500.vcf</D:href> <D:propstat> <D:status>HTTP/1.1 200 OK</D:status> <D:prop /> </D:propstat> <D:propstat> <D:status>HTTP/1.1 404 Not Found</D:status> <D:prop> <D:lockdiscovery /> </D:prop> </D:propstat> </D:response> </D:multistatus> Does Sogo support lock discovery in this manner? Perhaps someone sees an error? This list seems more related to end-user problems then for people developing against sogo. Am I in the right place, or is there a more appropriate mailing list? -- users@sogo.nu https://inverse.ca/sogo/lists
