To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=105464 Issue #|105464 Summary|WebDAV not performing locking Component|ucb Version|OOO310m19 Platform|Opteron/x86_64 URL| OS/Version|Linux Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|code Assigned to|mhu Reported by|topquark_net
------- Additional comments from [email protected] Tue Sep 29 21:00:00 +0000 2009 ------- The WebDAV UCB content provider in OOO310m19 does not appear to do any locking. This is a problem because some DAV servers (for example, the embedded DAV server used by Atlassian Confluence) require existing files to be locked before they can be written to. In addition, file locking is generally an essential requirement for remote/shared file access, to prevent data loss due to simultaneous editing of a file by multiple users. Here is an example of the DAV requests seen by an Apache 2.2 proxy sitting between an OOO310m19 client and an Apache 2.2 DAV server, and similar behavior is seen when contacting the Confluence DAV server (except that the PUT fails since the file has not been LOCKed): <Ask OO to open the file> "PROPFIND /test/test.doc HTTP/1.1" 207 543 "-" "-" "HEAD /test/test.doc HTTP/1.1" 200 - "-" "-" "GET /test/test.doc HTTP/1.1" 200 10240 "-" "-" "PROPFIND /test/test.doc HTTP/1.1" 207 543 "-" "-" <Make some changes and ask OO to save the file> "PROPFIND /test/ HTTP/1.1" 207 570 "-" "-" "PUT /test/test.doc HTTP/1.1" 204 - "-" "-" "PROPFIND /test/test.doc HTTP/1.1" 207 482 "-" "-" <Close the file> Locking IS performed by the OpenOffice provided by Ubuntu Jaunty (OOO300m15), however, the file is unlocked just before writing, and locked again just after writing: <Ask OO to open the file> "PROPFIND /test/test.doc HTTP/1.1" 207 543 "-" "-" "LOCK /test/test.doc HTTP/1.1" 200 402 "-" "-" "GET /test/test.doc HTTP/1.1" 200 11264 "-" "-" "PROPFIND /test/test.doc HTTP/1.1" 207 482 "-" "-" <Make some changes and ask OO to save the file> "UNLOCK /test/test.doc HTTP/1.1" 204 - "-" "-" "PROPFIND /test/test.doc HTTP/1.1" 207 543 "-" "-" "PROPFIND /test/test.doc HTTP/1.1" 207 500 "-" "-" "PROPFIND /test/test.doc HTTP/1.1" 207 482 "-" "-" "PROPFIND /test/test.doc HTTP/1.1" 207 1177 "-" "-" "GET /test/test.doc HTTP/1.1" 200 11264 "-" "-" "PUT /test/test.doc HTTP/1.1" 204 - "-" "-" "PROPFIND /test/test.doc HTTP/1.1" 207 482 "-" "-" "PROPFIND /test/test.doc HTTP/1.1" 207 543 "-" "-" "LOCK /test/test.doc HTTP/1.1" 200 402 "-" "-" "GET /test/test.doc HTTP/1.1" 200 10240 "-" "-" <Close the file> "UNLOCK /test/test.doc HTTP/1.1" 204 - "-" "-" This behavior in OOO300m15 is probably sufficient to prevent multiple people from accidentally editing the file simultaneously, but it still prevents the client from writing to a Confluence DAV server, since the file is unlocked at the instant when the file is written. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
