HTTP 507 — Insufficient Storage

Server error responses (5xx) · Updated 2026-10-18

HTTP 507 (WebDAV) is the disk-full response: the server cannot complete the method because storing the representation would exceed its capacity — the write equivalent of a full warehouse.

When 507 shows up

• Upload endpoints on volumes at capacity.
• Quota-bound WebDAV shares refusing further writes.

Mocking a 507 response

A response with this status can be faked end to end with a local mock rule — no backend changes needed. The configuration below mirrors the rule fields the ApiSimul editor uses (method, path, status, delay in milliseconds, response body):

{
  "method": "GET",
  "path": "/dav/upload",
  "status": 507,
  "delay": 260,
  "enabled": true,
  "body": {
    "error": "insufficient_storage",
    "quotaBytes": 1073741824
  }
}

Dynamic placeholders such as {{random.name}}, {{string.uuid}} or {{number.int 1 100}} can appear inside the body to vary each response, which keeps client-side list rendering and retry logic honest during development.

Frequently asked questions

What does HTTP 507 mean?
The server lacks the storage to complete the request. Freeing space or moving the payload elsewhere are the only paths forward.

How can I test a 507 response without a real backend?
Define a mock rule with the method and path your client requests and set the status to 507. The example configuration above returns this response after the listed delay, so the client exercises its 507 handling exactly as it would against a live server.

Related status codes

Need the response in your own project? Spin up rules for any status with the ApiSimul mock server, or browse every status code page.