https://bz.apache.org/bugzilla/show_bug.cgi?id=69362
--- Comment #5 from Michael Osipov <micha...@apache.org> --- (In reply to Mark Thomas from comment #4) > See RFC 4918 section 9.6.1. I think this should remain as is. Are you referring to: If any resource identified by a member URL cannot be deleted, then all of the member's ancestors MUST NOT be deleted, so as to maintain URL namespace consistency. Note that this does not change the behavior of DELETE, but the error reporting. Reading this: If an error occurs deleting a member resource (a resource other than the resource identified in the Request-URI), then the response can be a 207 (Multi-Status). Multi-Status is used here to indicate which internal resources could NOT be deleted, including an error code, which should help the client understand which resources caused the failure. For example, the Multi-Status body could include a response with status 423 (Locked) if an internal resource was locked. I understand that the current response is incomplete. Can you please elaborate? -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
