https://bz.apache.org/bugzilla/show_bug.cgi?id=62964
--- Comment #2 from Sarah Moy de Vitry <moydevi...@privasphere.com> --- (In reply to Mark Thomas from comment #1) > How are RFC 7807 error messages meant to be provided to WebDAV clients since > the WebDAV spec predates RFC 7807 and RFC 7807 provides no guidance on this. We can include the error messages in the same format but as xml content. Since the Versioning Extension of Webdav allows additional information to be included in the body of an error in xml format(https://www.greenbytes.de/tech/webdav/rfc4918.html#RFC3253) this could be a viable possibility. Also, since the WebDAV protocol inherits many properties from HTTP(which has deprecated the practice of including reasons in headers and moved towards including details in the error body) we assumed that Webdav will follow this trend and update accordingly. > Which WebDAV clients support RFC 7807 error messages? We are currently in contact with a few WebDAV clients who have expressed interest in supporting RFC 7807 error messages. > How will a client that hasn't adopted RFC 7807 behave in the presence of an > RFC 7807 error message? Clients that haven't adopted RFC 7807 should still be able to take decidable action based on the original status code alone with the additional information being superfluous to them. Another possibility is to have specific xml errors returned when certain preconditions and postconditions are violated as per [RFC4918] (https://www.greenbytes.de/tech/webdav/rfc4918.html#precondition.postcondition.xml.elements) which is specific to WebDAV. -- 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
