2072xx SuccessLow
HTTP 207 Multi-Status
Defined in RFC 4918
What Does HTTP 207 Mean?
The response body contains multiple status codes for multiple independent operations, typically in WebDAV scenarios.
Common Causes
- 1WebDAV batch file operations
- 2Bulk API operations with mixed results
- 3Multiple resource modifications in a single request
Impact
- ⚠Some operations may have succeeded while others failed
- ⚠Need to check individual status codes in response body
Ad Space – header
Developer Fix
For web developers and application engineers
- 1Parse the XML/JSON response body for individual statuses
- 2Handle partial success scenarios gracefully
- 3Report individual operation failures to the user
Server Admin Fix
For system administrators and DevOps engineers
- 1Monitor for recurring failures within multi-status responses
- 2Optimize batch operations to reduce partial failures
- 3Check WebDAV configuration for common error patterns
Ad Space – after-fix
Frequently Asked Questions
How do I parse a 207 Multi-Status response?
The response body is typically XML (for WebDAV) containing individual status elements for each sub-operation. Parse each status element to determine which operations succeeded or failed.
Is 207 used outside of WebDAV?
While defined for WebDAV, some REST APIs use 207 for batch operations where individual items may have different outcomes. However, this is not universally adopted.
Related HTTP Status Codes
About the Author
Web Infrastructure Team
Verified against official RFC specifications and real-world server configurations. HTTP status code behavior confirmed across Apache, Nginx, and Cloudflare.