207 Multi-Status

What HTTP 207 Multi-Status Means

Conveys status for multiple independent operations in a single response.

A WebDAV response whose XML body reports a separate status code for each resource affected by the request.

Common Causes

• WebDAV batch operations (PROPFIND, COPY, MOVE)
• Multiple sub-requests handled together

How to Fix It (For Visitors)

• No action needed - inspect individual statuses if needed

How to Fix It (For Developers/Admins)

• Return a multistatus XML body describing each resource
• Parse per-resource statuses on the client
• Use for bulk operations that can partially succeed

Returning a 207 Multi-Status (Code Examples)

If you build APIs or web apps, here is how to send an HTTP 207 response and how to test for it:

Node.js (Express)

app.get('/resource', (req, res) => {
  res.status(207).json({ error: 'Multi-Status' });
});

Python (Flask)

@app.route('/resource')
def resource():
    return jsonify(error='Multi-Status'), 207

PHP

<?php
http_response_code(207);
header('Content-Type: application/json');
echo json_encode(['error' => 'Multi-Status']);

Check the status with curl

curl -I https://example.com/resource
# Look for: HTTP/1.1 207 Multi-Status

Frequently Asked Questions

What does HTTP 207 Multi-Status mean?

A WebDAV response whose XML body reports a separate status code for each resource affected by the request. In short: Conveys status for multiple independent operations in a single response.

How should I handle an HTTP 207 Multi-Status response?

Return a multistatus XML body describing each resource. Parse per-resource statuses on the client. Use for bulk operations that can partially succeed.

Official Specification

The 207 Multi-Status status code is defined in RFC 4918 Section 11.1.

View the IANA HTTP Status Code Registry →