> and I'm sure it would happily not have a top-level status code (or a more meaningful one) itself anyway Fun thing to learn about: WebDAV introduced the HTTP

> and I'm sure it would happily not have a top-level status code (or a more meaningful one) itself anyway Fun thing to learn about: WebDAV introduced the HTTP 207 "Multi-Status" response status, for precisely the case where the response is actually a multi-response envelope. https://httpstatuses.com/207 https://httpstatuses.com/207 I often feel that the extra methods and features introduced by WebDAV would be usefully generalized to other analogous use-cases, like GraphQL. But then I recall that most of the WebDAV-specific stuff specifies XML-based request/response message formats, and quickly give up on the idea of any modern programmer doing it as a cool hack. Can't have "cool hack" and "XML" in the same sentence, after all ;)