507 Insufficient Storage
The server cannot store the representation needed to complete the request, because it is out of space.
At a glance
- Status code
- 507 Insufficient Storage
- Class
- 5xx, server error, the request looked fine and the server failed
- Defined in
- RFC 4918
- Cacheable by default
- no
- Response body
- Should say what ran out.
In detail
Defined for WebDAV but used more generally for disk or quota exhaustion. It is a resource problem, not a request problem.
Distinguish a per-user quota from a genuinely full disk in the body. They need completely different responses.
Retrying does not help unless something frees space. If it is a per-account quota, the client needs to delete something or upgrade.
Examples
HTTP/1.1 507 Insufficient Storage
Content-Type: application/json
{"error":"quota_exceeded","used":10737418240}Things that catch people out
- 413 is about the request being too large. 507 is about the server having nowhere to put it. Those are different fixes.
- A full disk often breaks logging first, so the 507 may be the only surviving evidence.
Try it: HTTP Request Builder
Build a request with any method, headers and body, send it, and read the status line the server returns.
HTTP Request Builder
LOCAL · Browser-OnlyBuild and test HTTP requests with custom headers and body
Authentication
Headers
Generate Code
curl -X GET 'https://api.example.com/endpoint' \
-H 'Content-Type: application/json'Showing a sample URL. Enter your endpoint above to update the snippet.
Related HTTP status codes
All http status codes →413 Content Too Large
The request body is larger than the server is willing to process. Formerly called Payload Too Large.
500 Internal Server Error
The server hit an unexpected condition and cannot say anything more specific. It is the catch-all for unhandled exceptions.
503 Service Unavailable
The server is temporarily unable to handle the request, because it is overloaded or deliberately down for maintenance. The condition is expected to clear.
508 Loop Detected
The server aborted the operation because it detected an infinite loop while processing a request with WebDAV bindings.
510 Not Extended
The server requires further extensions to the request before it will fulfil it. From an experimental extension framework that was never widely adopted.
511 Network Authentication Required
The client must authenticate to gain network access. This is the captive portal code, sent by the network rather than by the site you asked for.
Tools for this
- HTTP Request Builder Free online HTTP request builder - build and test HTTP requests with custom headers and body
- HTTP Headers Checker Free online HTTP headers checker - view HTTP response headers for any URL