Tomcat 7.0. Webdav returns 0x80070021
Tomcat 7.047. Default setup form web. Added an webapp with webdav enabled readonly = false; Windows 7: Mapped a drive to the specific folder: View content OK, put creating a new file/folder results in a dialog Localhost logging: 127.0.0.1 - - [03/Feb/2014:11:40:34 +0100] PROPFIND /webdav/dat1/New%20Text%20Document.txt HTTP/1.1 207 850 127.0.0.1 - - [03/Feb/2014:11:40:34 +0100] PROPFIND /webdav/dat1/New%20Text%20Document%20(2).txt HTTP/1.1 207 864 127.0.0.1 - - [03/Feb/2014:11:40:34 +0100] PROPFIND /webdav/dat1/New%20Text%20Document%20(3).txt HTTP/1.1 404 1011 127.0.0.1 - - [03/Feb/2014:11:40:34 +0100] PUT /webdav/dat1/New%20Text%20Document%20(3).txt HTTP/1.1 409 1001 Anyone familiar with this behavior, or known solutions. Thx in advance, Ruud This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law. If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone and with a 'reply' message. Thank you for your co-operation.
Re: Tomcat 7.0. Webdav returns 0x80070021
On 03/02/2014 10:43, Sampers, Ruud wrote: Tomcat 7.047. Default setup form web. Added an webapp with webdav enabled readonly = false; Windows 7: Mapped a drive to the specific folder: View content OK, put creating a new file/folder results in a dialog There is a long list of things that are broken in various versions of the Microsoft WebDAV client. You should try the WebdavFixFilter which identifies some of them and even fixes a few where it can. That said, I am sure there will be problems that that filter doesn't catch. I'll see if I have a Windows 7 client handy to test with and see if I can reproduce this. Mark Localhost logging: 127.0.0.1 - - [03/Feb/2014:11:40:34 +0100] PROPFIND /webdav/dat1/New%20Text%20Document.txt HTTP/1.1 207 850 127.0.0.1 - - [03/Feb/2014:11:40:34 +0100] PROPFIND /webdav/dat1/New%20Text%20Document%20(2).txt HTTP/1.1 207 864 127.0.0.1 - - [03/Feb/2014:11:40:34 +0100] PROPFIND /webdav/dat1/New%20Text%20Document%20(3).txt HTTP/1.1 404 1011 127.0.0.1 - - [03/Feb/2014:11:40:34 +0100] PUT /webdav/dat1/New%20Text%20Document%20(3).txt HTTP/1.1 409 1001 Anyone familiar with this behavior, or known solutions. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7.0. Webdav returns 0x80070021
On 03/02/2014 11:32, Mark Thomas wrote: On 03/02/2014 10:43, Sampers, Ruud wrote: Tomcat 7.047. Default setup form web. Added an webapp with webdav enabled readonly = false; Windows 7: Mapped a drive to the specific folder: View content OK, put creating a new file/folder results in a dialog There is a long list of things that are broken in various versions of the Microsoft WebDAV client. You should try the WebdavFixFilter which identifies some of them and even fixes a few where it can. That said, I am sure there will be problems that that filter doesn't catch. I'll see if I have a Windows 7 client handy to test with and see if I can reproduce this. Looks like Windows 7 only likes connecting on port 80. Not much Tomcat can do about that. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7.0. Webdav returns 0x80070021
Mark Thomas wrote: On 03/02/2014 11:32, Mark Thomas wrote: On 03/02/2014 10:43, Sampers, Ruud wrote: Tomcat 7.047. Default setup form web. Added an webapp with webdav enabled readonly = false; Windows 7: Mapped a drive to the specific folder: View content OK, put creating a new file/folder results in a dialog There is a long list of things that are broken in various versions of the Microsoft WebDAV client. You should try the WebdavFixFilter which identifies some of them and even fixes a few where it can. That said, I am sure there will be problems that that filter doesn't catch. I'll see if I have a Windows 7 client handy to test with and see if I can reproduce this. Looks like Windows 7 only likes connecting on port 80. Not much Tomcat can do about that. From memory of previous investigations, I think it is a bit more complicated : It wants either the connection to be https, or else it only accepts to be mapped to a root URL. In other words, something like : - map to https://server.company.com:443/somefolder/; is OK - map to http://server.company.com/somefolder/; is not OK - map to http://server.company.com/; is OK But, as you mentioned earlier, the list of inconsistencies and problems with the various Microsoft DAV client implementations is just about endless. We have resorted to using separate DAV clients instead (WebDrive e.g.). - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 7.0. Webdav returns 0x80070021
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 2/3/14, 7:39 AM, Mark Thomas wrote: On 03/02/2014 11:32, Mark Thomas wrote: On 03/02/2014 10:43, Sampers, Ruud wrote: Tomcat 7.047. Default setup form web. Added an webapp with webdav enabled readonly = false; Windows 7: Mapped a drive to the specific folder: View content OK, put creating a new file/folder results in a dialog There is a long list of things that are broken in various versions of the Microsoft WebDAV client. You should try the WebdavFixFilter which identifies some of them and even fixes a few where it can. That said, I am sure there will be problems that that filter doesn't catch. I'll see if I have a Windows 7 client handy to test with and see if I can reproduce this. Looks like Windows 7 only likes connecting on port 80. Not much Tomcat can do about that. Microsoft really broke their WebDAV client over time, and I've had to deal with a number of those issues until I had to finally give up with Windows 7 and use WebDrive (which has worked really well for us, BTW). I didn't know about any port-80 issues, though: we do everything over HTTPS and I do know that even over HTTPS, it requires that any authentication be done using HTTP-Digest -- you can't use HTTP-Basic. :( Ruud, can you try using another DAV client such as WebDrive (there is a time-limited trial you can download and install at no cost)? That will tell you whether your Tomcat configuration is correct or if the problem is with Microsoft's brain-dead WebDAV client. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJS79ngAAoJEBzwKT+lPKRYq74P/2h/dGGFoVJdi7UKZKctLUs1 638s3p96sN71M/TR82H7ckU9hlweoDAkB9oKwuttQRKkkvVKY1TaueYQ6ODth6+L RhD1D5YmkgpE9MaHWsEsEGd6L7gzndrEbPurLERIH89sbxBXxKC17fL3ASl+ojt2 8CgPjC9pLgH15FcAns5f8Ai+P33Iyzjti+v4ioLGOKrI1tDWD6xpY8wGpkFx57A8 BS4yDSOCjZvj/SDBqmADUGTaGuQnottC1YZ4hUKWG4SspQ4JJyO/2YgMXsrw7Cys vj+rptgBjos1ZHLIaANSPdYN+Qj4hWgszrYl1aAZ8hTNtmApOZ/D4nsk65fC7emm SiZz9jCEcRfmFZstL3l8RGCR/B8Ux/M3wdwyR0Sf/uuXBrh66iJWBf5Je4kVsBsW APgxXqc3aURn4LCqceaDMJGV8xAfYziCBwFEV3F2ZlmWZMTGc2thU6W53G3V9G/J uBCwjO38pYyo4alDCHmTZkotdnswiPkWX/H6ZsMQKfuw+Vmb+GMypCeTbcvB2myR 78AqkJNIVfHAT+pJ5Qu6AeXvsO1m46VcxkmRDEXsvGTHBP+OKA4IcpDyt3f5yd39 WrPYXHZ03QL2hds1ztlr7myquzfFZ1XWtc9vz2ImhS/y3C/e2XnSppaQufrKSlac Emg9Cu4QomqCaWUQKnX4 =l6O0 -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat 7.0. Webdav Returns 0x80070021
LS, Native apache WebDAV implementation is unable to reroute the root directory to another location. The error returned was induced by experimenting with aliases in different directories outside the tomcat context, the logging revealed that on that specific url (via the alias) the webdav protocol is not available. After several experiments conducted with paths, docBase and aliases I came to the conclusion that the only thing that was working is webdav enabled in the ROOT, without having the possibility to put your content outside the webdav folder. Windows 7 (with my test cases) was not the issue, I also tried cyberduck webdav (great tool btw) gave the same responses. What worked for my is the: servlet-class net.sf.webdav.WebdavServlet /servlet-class Implementation 2 JARs put in the lib directory: WEB-INF +\LIB + jcl-over-slf4j-1.7.5.jar + slf4j-api-1.7.5.jar + webdav-servlet-2.0.1.jar Plus the default webdav servlet descriptor in the web.inf , rootpath put c:/tmp. Worked out of the box. From this I mapped drives from windows 7 and cyberduck and it al worked great. Basic crud like you would expect. Happy coding! Ruud Sampers. This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law. If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone and with a 'reply' message. Thank you for your co-operation.
