best

HTTP Status Codesbest

Referenzhandbuch für alle HTTP-Statuscodes.

100

Continue

Server received request headers, client should proceed to send the body.

101

Switching Protocols

Server agrees to switch protocols per the client's Upgrade header.

200

OK

Request succeeded. The response body contains the result.

201

Created

Request succeeded and a new resource was created.

204

No Content

Request succeeded but no response body.

206

Partial Content

Partial resource returned (range requests).

301

Moved Permanently

Resource permanently moved to a new URL.

302

Found

Resource temporarily at a different URL.

304

Not Modified

Cached resource is still valid. Client should use cache.

307

Temporary Redirect

Redirect with same HTTP method.

308

Permanent Redirect

Permanent redirect preserving the HTTP method.

400

Bad Request

Server cannot process the request due to client error.

401

Unauthorized

Authentication required. Client must authenticate first.

403

Forbidden

Server understood request but refuses to authorize it.

404

Not Found

Resource not found at the given URL.

405

Method Not Allowed

HTTP method is not allowed for this resource.

408

Request Timeout

Server timed out waiting for request from client.

409

Conflict

Request conflicts with current state of the resource.

410

Gone

Resource permanently deleted and will not be available again.

413

Payload Too Large

Request body exceeds server's size limits.

414

URI Too Long

Request URI is too long for the server to process.

415

Unsupported Media Type

Request media type is not supported by the server.

422

Unprocessable Entity

Request is well-formed but contains semantic errors.

429

Too Many Requests

Client has sent too many requests (rate limiting).

500

Internal Server Error

Server encountered an unexpected condition.

501

Not Implemented

Server does not support the requested functionality.

502

Bad Gateway

Upstream server returned an invalid response.

503

Service Unavailable

Server temporarily unavailable (overloaded or down).

504

Gateway Timeout

Upstream server failed to respond in time.

How to use HTTP Status Codes

1

Geben Sie einen HTTP Status Code ein

Geben Sie einfach den HTTP-Statuscode ein, den Sie suchen, in die Suchleiste oben ein. Sie können auch unsere umfangreiche Liste von Statuscodes unten durchsuchen.

2

Finde die Bedeutung des Code

Unser Tool zeigt die Beschreibung und mögliche Ursachen für den HTTP Status Code an, den Sie eingegeben haben. Sie können auch verwandte Status Codes und technische Details erkunden.

3

Sparen Sie Zeit und verbessern Sie Ihre Development-Fähigkeiten

Mit unserem HTTP status codes reference guide haben Sie sofortigen Zugriff auf die Informationen, die Sie benötigen, um Probleme in Ihren Entwicklungsprojekten zu beheben und zu lösen.

Häufig gestellte Fragen

Verwandte Tools