Issue 74629 - Saving documents to a secure WebDAV fails
Summary: Saving documents to a secure WebDAV fails
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 2.0
Hardware: PC (x86_64) Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: needhelp
Depends on:
Reported: 2007-02-17 23:04 UTC by claudenw
Modified: 2014-02-12 14:41 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description claudenw 2007-02-17 23:04:08 UTC
A document in a secured WebDAV directory is read, modified and saved back; or a
new document is created and saved to the secured webDAV directory produces an
error window that reads:
"Error saving the document <document title>: The object can not be created in
directory http://server:80/directory/"

This functionality worked under 1.1.5

OO is configured to use OO dialog boxes.

Server is running Trustix 2.2 distro of linux.  uname -a returns:
Linux phoenix 2.4.28-4tr #1 Wed Nov 24 15:38:28 GMT 2004 i686 i686 i386 GNU/Linux

WebDAV service is provided by Apache 2.0.59.

The apache access log shows the following during the save of the document: - - [17/Feb/2007:17:51:02 -0500] "OPTIONS /performers/ HTTP/1.1" 401 - - claude [17/Feb/2007:17:51:02 -0500] "OPTIONS /performers/
HTTP/1.1" 200 - - - [17/Feb/2007:17:51:02 -0500] "PROPFIND /performers/ HTTP/1.1" 401 - - claude [17/Feb/2007:17:51:02 -0500] "PROPFIND /performers/
HTTP/1.1" 207 314 - - [17/Feb/2007:17:51:02 -0500] "PROPFIND /performers/ HTTP/1.1" 401 -

It appears that the DAV interface is not accepting the 207 (multi-status) status
code as valid.  The status code and its use is defined in RFC2518