DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=39384>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=39384 Summary: Dreamweaver 8 Webdav times out and fails Product: Tomcat 5 Version: 5.5.9 Platform: All OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Catalina AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] I've been implementing a webapp with webDAV functionality for a client, and have been hitting webDAV timeout problems when using Dreamweaver 8 as the client. I've searched google and bugzilla, and most of the articles are circa Tomcat 4, so I suspect there is something in the way the latest version of Dreamweaver is communicating that Tomcat doesn't know how to handle. A quick summary of my testing: - With my custom webapp, my own container (Winstone) works fine, Resin works fine and Tomcat locks up. - Even with tomcat's bundled webDAV application, Dreamweaver gets some intermittent errors to do with HTTP timeouts. Creating new folders brings up a dialog saying something like (rough translation from Japanese) "Can't GET remote folder information", but does it anyway. - This timeout problem occurs on 5.0.30 and 5.5.17. - The server believes that the response has been finished, but client hangs waiting. It seems to be just after a PROPFIND that is asking for lockdiscovery and resourcetype. - Other clients are fine (MS WebFolders, MS Office, Gnome DAV client) - My custom app is DAV level 2. >From looking at the headers passed back and forth, the main difference appears to be use of the Connection:close header (resin and winstone both use it in places that Tomcat doesn't). That leads me to believe that dreamweaver is confused when trying to keep-alive a tomcat connection that is closed by winstone and resin. I'm happy to continue trying to debug this, because I expect there's probably some webapp workaround that won't require any container changes, but I'd like to ask 2 questions: 1. Is there a tomcat debug setting that dumps headers and responses to the logs (so I can watch keep-alive behaviour while it's failing) ? I've looked and I couldn't see one. 2. Has anyone else had successful use of Dreamweaver 8 with Tomcat using webdav ? Thanks, Rick ---- Versions: Client - Dreamweaver 8.0.1 (Japanese version) Server - Tomcat, naked (ie no apache/IIS connector), v5.0.30, 5.5.9, 5.5.11 and 5.5.17 -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
