DevToolBoxKOSTENLOS
Blog

HTTP-Statuscode-Suche - Referenzhandbuch

Kostenloses Online-Tool zur HTTP-Statuscode-Suche. Durchsuchen Sie alle HTTP-Codes (100-599) mit detaillierten Beschreibungen und Lösungen.

100

Continue

1xx Informational

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

Common Examples:

  • File upload
  • Large POST request
101

Switching Protocols

1xx Informational

The requester has asked the server to switch protocols and the server agrees to do so.

Common Examples:

  • WebSocket upgrade
  • HTTP to HTTPS upgrade
103

Early Hints

1xx Informational

Used to return some response headers before final HTTP message.

Common Examples:

  • Link preloading
  • Resource hints
200

OK

2xx Success

The request succeeded. The result meaning depends on the HTTP method used.

Common Examples:

  • GET returns data
  • POST creates resource
  • PUT updates resource

Solutions:

  • Default response for successful HTTP requests. No action needed.
201

Created

2xx Success

The request succeeded and a new resource was created as a result.

Common Examples:

  • POST creates new user
  • POST creates new article
  • POST creates new order

Solutions:

  • The response should include a Location header with the URI of the new resource.
202

Accepted

2xx Success

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

Common Examples:

  • Async job queued
  • Background task started
  • Batch processing initiated

Solutions:

  • The server should provide a status URI where the client can check progress.
204

No Content

2xx Success

The request succeeded but there is no content to return.

Common Examples:

  • DELETE successful
  • PUT successful
  • Options request

Solutions:

  • Commonly used with DELETE or PUT requests. No response body is expected.
206

Partial Content

2xx Success

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

Common Examples:

  • Video streaming
  • Resume downloads
  • Large file downloads

Solutions:

  • Ensure Content-Range header is present in the response.
300

Multiple Choices

3xx Redirection

The request has more than one possible response.

Common Examples:

  • Multiple file formats available
  • Content negotiation fallback
301

Moved Permanently

3xx Redirection

The URL of the requested resource has been changed permanently.

Common Examples:

  • Domain migration
  • URL restructure
  • Old API endpoint deprecated

Solutions:

  • Update your bookmarks and links to use the new URL. Search engines will update their index.
302

Found

3xx Redirection

The URI of the requested resource has been changed temporarily.

Common Examples:

  • Temporary redirect
  • Maintenance page
  • Load balancing

Solutions:

  • Resubmit the request to the new location. The original URL is still valid.
303

See Other

3xx Redirection

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

Common Examples:

  • Form submission result
  • Post-Redirect-Get pattern
304

Not Modified

3xx Redirection

The resource has not been modified. Use your cached copy.

Common Examples:

  • Browser cache hit
  • ETag matches
  • Conditional GET request

Solutions:

  • Use the cached version of the resource. No need to re-download.
307

Temporary Redirect

3xx Redirection

The requested resource is temporarily at another URI, and the request method must not be changed.

Common Examples:

  • Temporary maintenance
  • Temporary load balancing
308

Permanent Redirect

3xx Redirection

The requested resource is permanently at another URI, and the request method must not be changed.

Common Examples:

  • Permanent migration
  • Protocol upgrade
400

Bad Request

4xx Client Error

The server cannot process the request due to client error (malformed request syntax).

Common Examples:

  • Invalid JSON
  • Missing required parameter
  • Invalid query string

Solutions:

  • Check request format and parameters
  • Verify headers are correct
  • Validate JSON payload
401

Unauthorized

4xx Client Error

Authentication is required and has failed or has not been provided.

Common Examples:

  • Missing API key
  • Invalid token
  • Expired session

Solutions:

  • Include valid authentication credentials
  • Refresh or regenerate your API key
  • Log in again
403

Forbidden

4xx Client Error

The client does not have access rights to the content.

Common Examples:

  • Insufficient permissions
  • Blocked IP address
  • Access restricted

Solutions:

  • Check your permissions
  • Request access from administrator
  • Use correct account
404

Not Found

4xx Client Error

The server cannot find the requested resource.

Common Examples:

  • Page deleted
  • Wrong URL
  • Endpoint no longer exists

Solutions:

  • Check the URL for typos
  • Check if the resource exists
  • Try a search instead
405

Method Not Allowed

4xx Client Error

The request method is not supported by the server for the requested resource.

Common Examples:

  • POST to read-only endpoint
  • DELETE on non-deletable resource

Solutions:

  • Use the correct HTTP method (GET, POST, PUT, DELETE, etc.)
  • Check API documentation
408

Request Timeout

4xx Client Error

The server timed out waiting for the request.

Common Examples:

  • Slow network
  • Large file upload
  • Server overloaded

Solutions:

  • Retry the request
  • Increase timeout settings
  • Check network connection
409

Conflict

4xx Client Error

The request conflicts with the current state of the server (e.g., version conflict).

Common Examples:

  • Duplicate entry
  • Version mismatch
  • Concurrent update conflict

Solutions:

  • Refresh data and retry
  • Resolve conflicts manually
  • Update to latest version
410

Gone

4xx Client Error

The requested resource is no longer available and will not be available again.

Common Examples:

  • Permanently deleted resource
  • Deprecated API
  • Archived content

Solutions:

  • The resource is permanently gone. Use alternative endpoints if available.
429

Too Many Requests

4xx Client Error

The user has sent too many requests in a given amount of time (rate limiting).

Common Examples:

  • Rate limit exceeded
  • Too many API calls
  • Brute force detection

Solutions:

  • Wait before retrying
  • Implement exponential backoff
  • Check rate limit headers
500

Internal Server Error

5xx Server Error

The server encountered an unexpected condition that prevented it from fulfilling the request.

Common Examples:

  • Code exception
  • Database error
  • Unhandled error

Solutions:

  • Retry the request
  • Contact support
  • Check server logs
501

Not Implemented

5xx Server Error

The server does not support the functionality required to fulfill the request.

Common Examples:

  • Feature not yet implemented
  • Unsupported HTTP method
502

Bad Gateway

5xx Server Error

The server received an invalid response from an upstream server.

Common Examples:

  • Proxy error
  • Load balancer issue
  • Upstream service down

Solutions:

  • Retry the request
  • Check upstream services
  • Check server configuration
503

Service Unavailable

5xx Server Error

The server is currently unable to handle the request due to maintenance or overload.

Common Examples:

  • Maintenance window
  • Server overloaded
  • Service temporarily down

Solutions:

  • Wait and retry later
  • Check status page
  • Contact support if it persists
504

Gateway Timeout

5xx Server Error

The server did not receive a timely response from an upstream server.

Common Examples:

  • Slow upstream server
  • Network timeout
  • Load balancer timeout

Solutions:

  • Retry the request
  • Check network connection
  • Wait and try again

HTTP Status Codes Reference

HTTP status codes are three-digit responses from a web server indicating the outcome of an HTTP request. They are grouped into five classes: 1xx (Informational), 2xx (Success), 3xx (Redirection), 4xx (Client Error), and 5xx (Server Error). Understanding these codes helps in debugging web applications and APIs.

Common Status Code Categories

  • 1xx Informational: Request received, continuing process
  • 2xx Success: Request succeeded (200 OK, 201 Created, 204 No Content)
  • 3xx Redirection: Further action needed (301 Moved, 302 Found, 304 Not Modified)
  • 4xx Client Error: Client request error (400 Bad Request, 404 Not Found, 401 Unauthorized)
  • 5xx Server Error: Server failed to fulfill request (500 Internal Error, 503 Service Unavailable)

Use Cases

  • Debugging API responses
  • Understanding HTTP error messages
  • Implementing proper error handling
  • Web development and server configuration
  • API testing and validation
𝕏 Twitterin LinkedIn

Bewerten Sie dieses Tool

4.8 / 5 · 175 Bewertungen

Bleiben Sie informiert

Wöchentliche Dev-Tipps und neue Tools.

Kein Spam. Jederzeit abbestellbar.

Enjoy these free tools?

Buy Me a Coffee