A 5xx server error: the server failed to fulfil an apparently valid request.

507
5xx · Server error

Insufficient Storage

The server cannot store the representation needed.

What it means

A WebDAV status: the method could not be performed because the server is unable to store the representation needed to complete the request.

When to use it

WebDAV-specific, returned when storage is exhausted.

RFC 4918 Not cacheable by default 5xx Server error

About HTTP Status Codes

This HTTP status codes directory covers every standard response code from the 1xx informational range through 5xx server errors. Each entry shows the numeric code, its canonical reason phrase and a one-line summary, and the whole list can be searched by number, name or meaning — 301, Unauthorized and timeout all find their targets — or filtered by response class.

Every code opens onto its own dedicated page with a full explainer: what the status actually means, when to use it in your own APIs and applications, whether responses with that code are cacheable by default, and the RFC that defines it. Related codes from the same class are linked at the bottom, so comparing 401 with 403 or 301 with 308 takes one click.

The five classes are the fastest mental model for reading any response: 1xx means the request is continuing, 2xx means success, 3xx means redirection, 4xx means the client made a mistake and 5xx means the server failed. The directory is organized around exactly that structure.

How to use HTTP Status Codes

  1. Type a code, a reason phrase or a keyword into the search box — for example 404, Not Found or redirect.
  2. Use the class filter to narrow the list to informational, success, redirection, client-error or server-error codes.
  3. Open any code’s page to read what it means, when to use it, its default cacheability and the defining RFC.
  4. Check the related-codes section to compare neighbors from the same class.
  5. Use the copy button to grab the code for a bug report, test or API spec.

Frequently asked questions

The first digit groups codes by outcome: 1xx informational (request received, keep going), 2xx success, 3xx redirection (further action needed), 4xx client error (the request is at fault) and 5xx server error (the server failed to fulfil a valid request).

401 Unauthorized means the request lacks valid authentication — the client should log in or supply credentials and retry. 403 Forbidden means the server understood the credentials but refuses access anyway: authentication won’t change the answer.

Use 301 when the resource has moved permanently — browsers and search engines update their references. Use 302 for temporary moves. If the request method must be preserved exactly, prefer their stricter modern counterparts, 308 and 307.

Some status codes, like 200 and 301, may be stored by browser and proxy caches even without explicit cache headers; others, like most 4xx and 5xx responses, may not. The flag tells you the default so you know when Cache-Control headers are required.

Yes. Each code gets a dedicated, linkable page with its meaning, typical use, cacheability and defining RFC, plus related codes from the same class — handy for bookmarking or sharing the exact code under discussion.

Yes. The directory and every per-code page are free to browse with no account, and search runs instantly in your browser without sending anything to the server.

Need help?
Found an issue with this tool? Let our team know.
Report an issue

Add this free tool to your own website — copy and paste the code below.