207 HTTP Origin: Network OSI layer 7 · Application Last updated 18 Nov 2026

HTTP 207 Multi-Status

A WebDAV response that carries several independent status codes in one XML body.

Exact message you may see HTTP 207 Multi-StatusHTTP/1.1 207 Multi-Statusstatus 207 multi-status<D:multistatus> response
Seen on: HTTP WebDAV

Meaning

Each resource in the XML <multistatus> has its own status, so a top-level 207 can still hide per-item failures (403, 423, 424). Parse every <response> and handle failures individually.

Common causes

  • WebDAV PROPFIND/COPY/MOVE touching many resources
  • Some items failed inside the XML
  • Client only checks the top-level status
  • Locked or forbidden members
  • Partial success treated as full

⚡ Quick fix

  1. Parse each <status> in the XML
  2. Retry or report the failed members
  3. Fix permissions/locks on the failing resources

Detailed fix by platform

cURL

  1. curl -i -X PROPFIND -H "Depth: 1" https://dav.example.com/folder/

How to diagnose

  1. Per-item status — Checked?
  2. Failures — Which members?
  3. Locks — Present?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

102 — HTTP 102 Processing (HTTP)102201 — HTTP 201 Created (HTTP)201202 — HTTP 202 Accepted (HTTP)202203 — HTTP 203 Non-Authoritative Information (HTTP)203204 — HTTP 204 No Content (HTTP)204423 — HTTP 423 Locked (HTTP)423424 — HTTP 424 Failed Dependency (HTTP)424507 — HTTP 507 Insufficient Storage (HTTP)507207

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.