tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 3613] New: - webdav bugs in some operations
Date Fri, 14 Sep 2001 14:27:53 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3613>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3613

           Summary: webdav bugs in some operations
           Product: Tomcat 4
           Version: 4.0 Release Candidate 1
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: account.consult-smi@airbus.fr


webdav works only for certain security configurations.

As webdav clients I use IE5 or IE5.5 or FileExplorer; all on a win2000 OS.
I can always see the directory tree and the files and read-operations work fine 
as well. However, depending on the security configuration of the webdav webapp, 
some features of webdav fail.

If the webdav-webapp is configured to allow http and to have no authentication, 
then everything seems to work fine.

If the webdav-webapp is configured to inforce(!) HTTPS access by specifing a 
transport guarantee of "CONFIDENTIAL", then I cannot RENAME files and I cannot 
copy a file from the client to the server, overwriting a file there. However, 
copying a file to the server, which is not already there, works fine. File 
Deletion works as well. Directories can be queried, files can be read.

If the webdav-webapp is configured to inforce(!) HTTPS access by specifing a 
transport guarantee of "CONFIDENTIAL" and is furthermore configured to have a 
CLIENT-CERT authentication, then copying files to the server doesn't work at 
all. Renaming also doesn't work. Directories can be queried, files can be read.

(I have set the read-only attribute in the webdav web.xml to "false".)

Mime
View raw message