HTTP-Status-Referenz

Durchsuchen Sie HTTP-Statuscodes (1xx–5xx) mit Beschreibungen.

Ihre Daten verlassen niemals Ihren Browser

100

Continue

The server has received the request headers and the client should proceed to send the request body.

101

Switching Protocols

The server is switching protocols as requested by the client, for example upgrading from HTTP to WebSocket.

102

Processing

The server has received and is processing the request, but no response is available yet (WebDAV).

103

Early Hints

Used to return some response headers before the final HTTP message, allowing the client to preload resources.

200

OK

The request has succeeded. The meaning depends on the HTTP method (GET, POST, PUT, DELETE, etc.).

201

Created

The request has been fulfilled and resulted in a new resource being created, typically after a POST request.

202

Accepted

The request has been accepted for processing but the processing has not been completed yet.

203

Non-Authoritative Information

The returned metadata may be from a third-party copy rather than the origin server.

204

No Content

The server successfully processed the request and is not returning any content body.

205

Reset Content

The server successfully processed the request and asks the client to reset the document view.

206

Partial Content

The server is delivering only part of the resource due to a range header sent by the client.

300

Multiple Choices

The request has more than one possible response. The user or user agent should choose one of them.

301

Moved Permanently

The URL of the requested resource has been changed permanently. The new URL is given in the response.

302

Found

The requested resource resides temporarily under a different URI. The client should continue to use the original URI.

303

See Other

The server sent this response to direct the client to get the requested resource at another URI with a GET request.

304

Not Modified

Indicates that the resource has not been modified since the version specified by the request headers (used for caching).

307

Temporary Redirect

The server sends this response to direct the client to a different URI, but the client must use the same HTTP method.

308

Permanent Redirect

The resource is now permanently located at another URI, and the client must use the same HTTP method for future requests.

400

Bad Request

The server cannot or will not process the request due to something that is perceived to be a client error (malformed syntax).

401

Unauthorized

The client must authenticate itself to get the requested response. Often called "unauthenticated" rather than "unauthorized".

403

Forbidden

The client does not have access rights to the content; the server is refusing to give the requested resource.

404

Not Found

The server can not find the requested resource. This is the most well-known HTTP error status code.

405

Method Not Allowed

The request method is known by the server but is not supported by the target resource.

408

Request Timeout

The server timed out waiting for the request from the client. The client may repeat the request without modifications.

409

Conflict

The request could not be completed due to a conflict with the current state of the target resource.

410

Gone

The requested content has been permanently deleted from the server, with no forwarding address.

413

Payload Too Large

The request entity is larger than limits defined by the server; the server might close the connection or return a Retry-After header.

414

URI Too Long

The URI requested by the client is longer than the server is willing to interpret.

415

Unsupported Media Type

The media format of the requested data is not supported by the server, so the server is rejecting the request.

418

I'm a teapot

The server refuses the attempt to brew coffee with a teapot. This is an April Fools joke from RFC 2324 (HTCPCP).

422

Unprocessable Entity

The request was well-formed but was unable to be followed due to semantic errors (WebDAV).

429

Too Many Requests

The user has sent too many requests in a given amount of time ("rate limiting"). The response should include a Retry-After header.

451

Unavailable For Legal Reasons

The server is denying access to the resource as a consequence of a legal demand (e.g., censorship or copyright).

500

Internal Server Error

The server has encountered a situation it does not know how to handle. This is a generic server error response.

501

Not Implemented

The request method is not supported by the server and cannot be handled. The server either does not recognize the request method or lacks the ability to fulfill it.

502

Bad Gateway

The server, while acting as a gateway or proxy, received an invalid response from the upstream server.

503

Service Unavailable

The server is not ready to handle the request. Common causes are server maintenance or temporary overloading.

504

Gateway Timeout

The server, while acting as a gateway or proxy, did not get a response in time from the upstream server.

Anleitung

Codes durchstöbern: Die vollständige Liste nach Kategorien von 1xx bis 5xx organisierte Liste durchscrollen.
Suche: Eine Codenummer wie 502 oder ein Schlüsselwort wie redirect eintippen, um sofort zu filtern.
Filtern: Die Liste auf eine Kategorie eingrenzen — informativ, Erfolg, Umleitung, Client-Fehler oder Server-Fehler.

Die fünf Kategorien verstehen

HTTP-Statuscodes sind nach ihrer ersten Ziffer gruppiert, und die Gruppen zu kennen macht das Debugging viel schneller. Codes im 1xx-Bereich sind informativ und von Nutzern selten zu sehen — 101 Switching Protocols etwa erscheint, wenn sich eine Verbindung zu WebSocket aufrüstet. Die 2xx-Familie bedeutet Erfolg: 200 OK ist der Normalfall, während 201 Created und 204 No Content API-Clients genau sagen, was passiert ist.

Die 3xx-Codes behandeln Umleitungen, und die Unterscheidung zwischen 301 (permanent) und 302 (temporär) ist für SEO enorm wichtig, weil nur ein 301 Link-Equity an die neue URL weiterreicht. Die berühmten 4xx-Codes signalisieren Client-Fehler — 400 für fehlerhafte Anfragen, 401 für fehlende Authentifizierung, 403 für unzureichende Berechtigung, 404 für fehlende Ressourcen und 429, wenn Sie gedrosselt werden. Schließlich bedeuten 5xx-Codes, dass der Server selbst ausfiel: 500 ist ein generischer Absturz, 502 heißt, ein Upstream-Dienst (etwa die App hinter Ihrem Reverse-Proxy) hat schlecht geantwortet, und 503 bedeutet meist, dass der Dienst vorübergehend nicht erreichbar ist, oft während eines Deploys.

Funktionen

Vollständige Liste der standardmäßigen HTTP-Statuscodes
Suche nach Codenummer oder Beschreibung
Kategorienfilter (1xx–5xx)
Farbkodierte Kategorien für schnelles Scannen
Erklärungen in einfacher Sprache, nicht nur RFC-Jargon

Anwendungsfälle

Unbekannte Fehler eines Drittanbieter-API entschlüsseln
Load-Balancer- und Reverse-Proxy-Logs interpretieren (502 vs. 504)
Korrekte Fehlerbehandlung im Client-Code schreiben
HTTP-Grundlagen Junior-Entwicklern vermitteln

Häufig gestellte Fragen

Was ist der HTTP-Statuscode 404?

404 Not Found bedeutet, dass der Server die angeforderte Ressource nicht finden kann.

Was ist der Unterschied zwischen 401 und 403?

401 bedeutet, dass eine Authentifizierung erforderlich ist. 403 bedeutet, dass Ihnen die Berechtigung fehlt.