| Previous | Next |
| HTTP_STATUS_PARTIAL_CONTENT | HTTP_STATUS_ALREADY_REPORTED |
HTTP_STATUS_MULTI
The response body is an XML multistatus document. Each response element can contain a different status, so the outer 207 status does not mean every requested resource succeeded.
When troubleshooting, inspect every embedded status and resource URL. A client should report partial failure instead of collapsing the whole operation into a single success or error message.
Operational meaning of HTTP 207 for HTTP_STATUS_MULTI
HTTP 207 (this result) is a successful response. AllStat records its meaning as “207 Multi-Status”. Interpret it with the request method, selected representation, response headers, and the specification or product that defines the code; the number alone does not prove that application work completed.
Client and server handling
- Verify what work the response representation says was completed; this result can still describe asynchronous or partial handling.
- use validators, location/status links, and application identifiers supplied by the server.
- do not retry a non-idempotent request merely because the client did not understand the response body.
For telemetry, record HTTP 207, method, authority, route template rather than secrets, response headers relevant to caching or retry, latency, upstream identity, and whether the response originated at the application or an intermediary.
Looking for a different code? Search another status or error code.