---
title: "HTTP 507 Insufficient Storage: meaning and fixes"
url: https://proxy.wiki/glossary/http-status-507/
type: Glossary Term
author: "proxy.wiki editorial"
published: 2026-10-21
updated: 2026-10-21
site: proxy.wiki
topics: ["Web scraping"]
license: CC BY 4.0; quote freely with attribution to https://proxy.wiki/
---

# HTTP 507 Insufficient Storage: meaning and fixes

> HTTP 507 Insufficient Storage means the server cannot store the representation needed for the request. Check quota and disk before retrying uploads.

HTTP 507 means a WebDAV server cannot store the representation needed to complete the request: “Insufficient Storage”. RFC 4918 [section 11.5](https://www.rfc-editor.org/rfc/rfc4918#section-11.5) defines it as a temporary condition. The shortage can be filesystem space, a per-user quota or a collection limit. It is different from 413, which rejects a request because its body exceeds a request-size limit before storage is attempted.

507 is registered for WebDAV, but storage APIs sometimes reuse it for a quota refusal. A forward proxy normally relays the response. A proxy that runs its own upload quota may answer 403 or 507 before the origin sees bytes, so compare the response signer and the uploaded byte count.

## Reproduce a quota refusal

The local Python 3.15.0 quota server accepted a one-mebibyte upload and rejected a three-mebibyte upload before reading it:

```
from http.server import BaseHTTPRequestHandler, HTTPServer

class H(BaseHTTPRequestHandler):
    def do_PUT(self):
        length = int(self.headers.get("Content-Length", 0))
        if length > 2 * 1024 * 1024:
            body = b"quota exceeded: free space before retrying\n"
            self.send_response(507)
            self.send_header("Content-Length", str(len(body)))
            self.end_headers()
            return
        self.rfile.read(length)
        self.send_response(201)
        self.send_header("Content-Length", "0")
        self.end_headers()

HTTPServer(("127.0.0.1", 47517), H).serve_forever()
```

```
$ curl -s -o /dev/null -w "%{http_code} sent=%{size_upload}\n" -T one-mib.bin http://127.0.0.1:47517/a.bin
201 sent=1048576

$ curl -si -w "sent=%{size_upload}\n" -T three-mib.bin http://127.0.0.1:47517/b.bin
HTTP/1.0 507 Insufficient Storage
Server: BaseHTTP Python/3.15.0
Content-Length: 43

quota exceeded: free space before retrying
sent=0
```

The capture used curl 8.7.1 and files created locally. A second run against Apache httpd 2.4.67 with `mod_dav_fs` returned 507 after receiving the full three-mebibyte body. That difference is important: a server may discover the shortage only after reading the representation. A proxy or client that retries the upload can therefore send the whole body again.

## Storage versus request limits

Ask which resource is full. Filesystem space is global. A WebDAV quota is often scoped to a principal or collection, and RFC 4331 describes the `DAV:quota-used-bytes` and `DAV:quota-available-bytes` properties. An API may return 507 when an account’s object or byte allowance is exhausted. The body, a quota property or the provider’s documentation should say which one.

A 507 through Squid 6.13 retained the origin status when the proxy was only forwarding. A proxy-side refusal had the proxy’s own headers and a different status in the test rig. Never infer the storage owner from the numeric code alone.

For uploads, send a size check or a resumable request when the API supports one. On a server you operate, expose free-space and quota metrics and reject before reading a large body when possible. For a crawler, stop retrying until the storage owner confirms recovery.

## Causes and fixes

| Cause | How to confirm it | What to change |
| --- | --- | --- |
| WebDAV collection quota is full | PROPFIND exposes quota properties or the body names the collection | Delete or archive permitted resources, or request more quota |
| Filesystem has no free space | Origin logs and host metrics show a full volume | Free space or expand the volume before retrying |
| Per-account object or byte allowance | API body identifies the account and a quota reset policy | Use the documented quota path; do not rotate proxy exits |
| Proxy upload quota | Proxy signs the response and the origin records no upload | Check the proxy plan or route policy |
| Large body reaches the server before rejection | curl reports uploaded bytes equal to the file size | Use a preflight or resumable upload and set retries to zero for the body |
| Confused 413 configuration | Small body fails at a fixed request-size threshold | Inspect request-body limits separately from storage and quota |

Read [413 Content Too Large](/glossary/http-status-413/) when the rejection is a request-size ceiling, and use the [curl proxy guide](/guides/how-to-use-a-proxy-with-curl/) to compare an origin upload with a proxied one. A new exit IP cannot create disk space or quota.

Before resending a large body, determine whether the server read it and whether the operation is safe to repeat. A quota reset, free-space check or resumable upload is a better recovery signal than a different proxy address. Preserve the response headers and upload byte count so the storage owner can distinguish a preflight refusal from a late write failure.

## Frequently asked questions

### Is 507 temporary?

RFC 4918 describes it as temporary, but the reset may require an operator or quota change.

### Is 507 the same as 413?

No. 413 is a request-content limit. 507 means the server cannot store what the method requires.

## Sources

1. [RFC 4918 section 11.5: 507 Insufficient Storage](https://www.rfc-editor.org/rfc/rfc4918#section-11.5)
2. [RFC 4331: WebDAV Quotas](https://www.rfc-editor.org/rfc/rfc4331)
