DevToolBoxZA DARMO
Blog

Referencja kodów statusu HTTP

Sprawdź kody statusu HTTP: 1xx, 2xx, 3xx, 4xx, 5xx.

100
Continue
Server received request headers
101
Switching Protocols
Upgrade requested
200
OK
Request succeeded
201
Created
Resource created
204
No Content
Success, no body
301
Moved Permanently
Redirect permanently
302
Found
Temporary redirect
304
Not Modified
Use cached version
400
Bad Request
Invalid syntax
401
Unauthorized
Authentication required
403
Forbidden
Access denied
404
Not Found
Resource not found
405
Method Not Allowed
HTTP method not allowed
422
Unprocessable Entity
Validation error
429
Too Many Requests
Rate limit exceeded
500
Internal Server Error
Server error
502
Bad Gateway
Invalid response from upstream
503
Service Unavailable
Server overloaded
𝕏 Twitterin LinkedIn

Oceń to narzędzie

3.7 / 5 · 172 ocen

Bądź na bieżąco

Otrzymuj cotygodniowe porady i nowe narzędzia.

Bez spamu. Zrezygnuj kiedy chcesz.

Enjoy these free tools?

Buy Me a Coffee

How to Use

  1. Browse the status codes by category (1xx through 5xx)
  2. Click on any code to see its detailed description
  3. Use the search box to find a specific code quickly
  4. Review the use cases to understand when to return each code

Common Use Cases

  • Designing REST API response codes
  • Debugging HTTP errors in web applications
  • Learning about HTTP protocol standards
  • Documenting API error handling behavior

Frequently Asked Questions

What is the difference between 401 and 403?
401 Unauthorized means the client has not provided valid authentication credentials. 403 Forbidden means the client is authenticated but does not have permission to access the resource.
When should I use 200 vs 201 vs 204?
Use 200 OK for successful GET requests, 201 Created when a new resource is created (POST), and 204 No Content for successful requests with no response body (DELETE).
What does a 502 Bad Gateway error mean?
502 means the server acting as a gateway received an invalid response from an upstream server. It usually indicates a problem with the backend service, not the client.