On 2024/10/02 14:30:52 Christopher Schultz wrote: > All, > > On 10/2/24 06:21, Mark Thomas wrote: > > -1 veto > > > > This change is not compliant with RFC 9110. > > > > [...] > > > > Generally, SC_METHOD_NOT_ALLOWED is probably the right status code as > > the most likely failure mode is a lack of permissions. I just wonder if > > there are circumstances where we would want to return > > SC_INTERNAL_SERVER_ERROR and how we would determine if that were the case. > > I think METHOD_NOT_ALLOWED is inappropriate. The method is only "not > allowed" if the whole of the WebDAV share is read-only. Anything else > should be some other kind of response IMO.
Here is a counter example we cannot cover, the servlet is set to read-write, but the resouce is explicitly set to read-only. This cannot be reflected in the response, unfortunately. > On Windows, file-in-use will block a DELETE, even if the permissions are > okay for that file. DELETE may succeed if you try again when the file is > not in use. > > I'm sure other examples exist. True, but that would us need to know to send a retry header. Hard to cover all cases. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
