rmaucher commented on PR #771: URL: https://github.com/apache/tomcat/pull/771#issuecomment-2434585666
All of the WebDAV methods are "must not cache" actually (except PROPFIND, but IMO it's a bad idea to cache it), and it is 100% obvious why. If the proxy feels like it doesn't have to send the MKCOL to Tomcat, things are not going to work. I don't know if the WebDAV Servlet should have built in headers for that or the users should use a valve, filter or something instead (like the obvious: DO NOT use a caching proxy on the WebDAV location !). Personally I am "done" with the WebDAV Servlet. The area had no tests (Litmus was sometimes run manually by Mark it seems) so according to our previous meetings there was a need to improve that. Along the way I found design problems and bugs I had to fix, and it now seems good enough (Litmus passes and the testcase scenarios are rather complex). I don't believe there are lots of users for this, so as far as I am concerned it is more than enough. When adding tests, you might want to look at that: https://nightlies.apache.org/tomcat/tomcat-12.0.x/coverage/org.apache.catalina.servlets/index.html#dn-a You can set test.coverage=true (and also add execute.validate=true) in your build.properties to see if new tests improve that or if things were already covered. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
