Is a 507 my problem or the server's?
It depends. If your account quota is full, freeing space fixes it. If the server disk is full, only the administrator can resolve it.
HTTP 507 INSUFFICIENT STORAGE
WebDAV: the server cannot store what the request needs. 507 belongs to the 5xx server error class and is defined in RFC 4918.
Loading the workbench.
About HTTP 507
What Does HTTP 507 Insufficient Storage Mean?
WebDAV: the server cannot store what the request needs. The code is registered with IANA and defined in RFC 4918.
Server error: the server failed to fulfill a valid request. Every code from 500 to 599 shares that general meaning, so a client that does not recognise 507 must treat it like 500.
When Do You See a 507 Response?
507 Insufficient Storage is a WebDAV status meaning the server cannot store the representation needed to complete the request. The disk may be full, the user may have exceeded a storage quota, or a filesystem limit may have been reached. You see it from Nextcloud, ownCloud, SharePoint, and other WebDAV-based file servers during uploads or copies, and some object stores and APIs reuse it for quota errors.
How Do You Fix a 507?
Users should free space or ask for a larger quota, then retry the upload. Administrators should check disk usage, quota settings, and temporary directories, which often fill up first during large uploads. Servers should return 507 rather than a generic 500 so clients can show a clear out-of-space message. For non-WebDAV APIs where the limit is a plan quota, 413 or 403 may communicate better.
What Does a 507 Response Look Like?
HTTP/1.1 507 Insufficient Storage
Content-Type: application/xml; charset=utf-8507 is not cacheable by default: a browser or CDN stores it only when Cache-Control or Expires explicitly allows it.
To inspect a real one without sending it anywhere:
- Copy the response headers from your browser Network tab, or from
curl -i. - Paste them into the Header decoder to see every header explained.
- Check caching in the Cache lane.
Which Status Codes Are Related to 507?
- 413 Content Too Large: The body is bigger than the server accepts. Formerly "Payload Too Large".
- 500 Internal Server Error: A generic server failure, usually an unhandled exception.
- 423 Locked: WebDAV: the resource is locked.
Browse every code on the HTTP status codes page.
What Other Lanes Are in the Reference Section?
- HTTP status codes: Every IANA-registered status code, with a page per code.
- MIME types: File extensions to Content-Type, searchable both ways, plus a Content-Type parser.
- HTTP methods: GET, POST, PUT, PATCH, DELETE and the rest: safe, idempotent, cacheable.
Elsewhere in 2http: Header decoder, Cookie decoder, Cache-Control decoder, CORS checker, User-agent parser, and all eleven lanes on the 2http home page. Part of the 2suite.io privacy-first ecosystem.
Frequently Asked Questions
Can 507 happen on non-WebDAV sites?
It is defined by WebDAV, but some file APIs and storage services use it to report quota or disk problems.
Is HTTP 507 an error?
Yes. 507 is a server error response: the server failed to handle a valid request, so retrying later may work.
Is a 507 response cacheable by default?
No. Caches store a 507 only when Cache-Control or Expires explicitly allows it.
How Can You Verify That Nothing Leaves This Browser?
You do not have to take our word that your headers stay here. Developer tools show every request a page makes, so you can watch this page work and confirm that nothing is sent. The check takes under a minute.
- Open your browser developer tools with
F12, orCmd+Option+Ion a Mac, and select the Network tab. - Reload the page and let it finish. You will see the page's own files, its web fonts, and one anonymous page-view request. Nothing has been typed yet, so none of them can contain your headers.
- Click the clear icon in the Network tab so that the log is empty.
- Paste real headers into any lane and read the result.
- Look at the Network tab again. It is still empty. For extra proof, turn on offline mode after the page loads and every lane keeps working.
Only two things can add a line to that log, and neither carries your headers. Submitting the feedback form sends the vote and comment you typed. Typing characters in a script the page has not displayed yet, such as Cyrillic or Greek, can make the browser fetch the matching font file, and that request names only the font.
2http never sends a request on your behalf: the request builder writes code for you to run, and the meta inspector reads source you paste instead of fetching a URL. The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site and the anonymous analytics endpoint.