507 Insufficient Storage
The 507 Insufficient Storage HTTP status code indicates the server does not have enough free storage to perform the operation. The client can re-try the operation at some time in the future when more storage becomes available.
This status code is defined by WebDAV, but available for use in any application.
Writing responses (servers)
Servers should produce 507 Insufficient Storage
when the operation requires free disk space, but not enough is available to complete the operation. 500 Internal Server Error
can also be used for this error, but it is less specific.
Servers should link to a system status page that provides any progress updates from the system administrator, and customer service contact information.
See also: Message body exceeds resource limits
If the server technically has the space to accept an upload, but would prefer not to because it exceeds a specified resource limit, this is considered a user error and not a server error, see 413 Payload Too Large instead.
Reading responses (clients)
Typically this requires user intervention, either the attention of the system administrator, or the user confirming out-of-band that the system is back into regular operation, before retrying the request.
If the server specifies Retry-After, this might signal that additional storage is being automatically provisioned, and clients may automatically retry an upload after the given duration. Clients should send Expect: 100-continue when making uploads, to not waste bandwidth on a request that will likely be rejected.
Overview table
- Name
- 507
- Message
- 507 Insufficient Storage
- Description
- The server cannot fill the request because it is out of storage space.
- Specification
- RFC 4918: HTTP Extensions for Distributed Authoring (WebDAV)
Example
HTTP/1.1 507 Insufficient Storage