For a plain file, OPTIONS returns "PROPPATCH" as allowed method ("Allow" header). However, an attempt to PROPPATCH the resource returns a 405 status ("not allowed"). Issues here: - If PROPPATCH is not allowed, OPTIONS should say so - RFC2616 (section 10.4.6) requires returning an "Allow" header whenever the response was a 405 (this doesn't happen)
I have a patch for this bug which I will attach. Currently PROPPATCH always returns 405 as it hasn't been implemented. The patch changes this to return 501 (not implemented). Even with the patch, this bug should be left open with a severity of enhancement until this functionality is developed. There are a number of places where a 405 responses is returned and none of them set the allow header. The patch also addresses this.
Created attachment 9100 [details] Patch for TC5 to fix this bug.
I've applied your patch, thanks.
Procedural question: this was reported against Tomcat4, but was resolved in Tomcat5. Shouldn't the issue be left open? What's the general policy about reporting/resolving issues in Tomcat4 and Tomcat5? If the problem applies to both, should it reported twice?
When I have fixed all the webdav issues, I'll put them all together into a combined TC4 patch.
Sounds great, thanks.