DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24006>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24006 PROPPATCH vs Allow header Summary: PROPPATCH vs Allow header Product: Tomcat 4 Version: 4.1.27 Platform: Other URL: http://greenbytes.de/tech/webdav/rfc2616.html#status.405 OS/Version: Other Status: NEW Severity: Minor Priority: Other Component: Servlets:WebDAV AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] 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) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]