2xx SuccessHTTP Status Code Reference

HTTP 207 Multi-Status— What It Means, Causes & How to Fix It

The response contains multiple status codes for different sub-requests, conveying information about multiple resources in situations where multiple status codes might be appropriate. Primarily used with WebDAV.

Live URL Status Checker

Enter any URL to see its real HTTP response code

Common Causes

  • WebDAV batch operations on multiple resources
  • Bulk API operations with mixed success/failure results
  • File operations across multiple directories

How to Fix

  1. 1Parse the XML/JSON body to check individual operation statuses
  2. 2Retry failed sub-operations individually
  3. 3Check permissions for each resource in the batch

Example

HTTP 207 Multi-Status
PROPFIND /files HTTP/1.1

→ 207 Multi-Status
→ XML body with individual status for each file

Related Success Codes

200

OK

201

Created

202

Accepted

203

Non-Authoritative Information

204

No Content

205

Reset Content

206

Partial Content

208

Already Reported

226

IM Used

Commonly Referenced Status Codes

The most frequently searched HTTP status codes

200OK201Created204No Content301Moved Permanently302Found400Bad Request401Unauthorized403Forbidden404Not Found422Unprocessable Content429Too Many Requests500Internal Server Error502Bad Gateway503Service Unavailable504Gateway Timeout

Related Tools

HTTP Status LookupAPI Request BuildercURL GeneratorHTTP Header ViewerHTTP Header DiffRedirect Checker