Github user markt-asf commented on the issue:

    https://github.com/apache/tomcat/pull/96
  
    No argument with Konstantin's points here. I started to look at 
implementing this and I realised that the WebDAV is inconsistent with how the 
allow header is generated. A method may not be included in the allow header but 
will not generate a 405 if that method is used for the same resource. That 
seems wrong to me.
    Before I start changing this, I'm going to put together a simple test case 
to check it and dig out the WebDAV test suite we have used in the past to make 
sure my changes don't break anything. This is probably going to delay the tag 
by a day or so.


---

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to