Developer Tools
Web UtilitiesReferência de Códigos de Status HTTP
Referência completa de todos os códigos de status HTTP (1xx-5xx) com explicações detalhadas. Ideal para desenvolvedores web e administradores de sistemas que depuram respostas HTTP.
1xx - Informational
Request received, continuing process
Continue
The client should continue with its request
Switching Protocols
The server is switching protocols as requested by the client
Processing
The server is processing the request but no response is available yet
Early Hints
Used to return some response headers before final HTTP message
2xx - Success
The action was successfully received, understood, and accepted
OK
The request was successful
Created
The request was successful and a new resource was created
Accepted
The request has been accepted for processing, but processing is not complete
Non-Authoritative Information
The returned meta-information is not definitive
No Content
The request was successful but there is no content to return
Reset Content
The client should reset the form that caused this request to be sent
Partial Content
The server is delivering only part of the resource due to a range header
Multi-Status
The message body contains multiple status codes for different operations
Already Reported
The members of a DAV binding have already been enumerated
IM Used
The server has fulfilled a request using an instance manipulation
3xx - Redirection
Further action must be taken in order to complete the request
Multiple Choices
There are multiple options for the resource from which the client may choose
Moved Permanently
The resource has been permanently moved to a new URL
Found
The resource temporarily resides under a different URL
See Other
The response can be found under a different URL using GET method
Not Modified
The resource has not been modified since the last request
Use Proxy
The requested resource must be accessed through the proxy given by the Location field
Temporary Redirect
The request should be repeated with another URL but future requests should still use the original URL
Permanent Redirect
The request and all future requests should be repeated using another URL
4xx - Client Error
The request contains bad syntax or cannot be fulfilled
Bad Request
The server cannot process the request due to a client error
Unauthorized
Authentication is required and has failed or has not yet been provided
Payment Required
Reserved for future use
Forbidden
The request was valid, but the server is refusing action
Not Found
The requested resource could not be found
Method Not Allowed
The request method is not supported for the requested resource
Not Acceptable
The requested resource is capable of generating only content not acceptable according to Accept headers
Proxy Authentication Required
The client must first authenticate itself with the proxy
Request Timeout
The server timed out waiting for the request
Conflict
The request could not be processed because of conflict in the request
Gone
The resource requested is no longer available and will not be available again
Length Required
The request did not specify the length of its content
Precondition Failed
The server does not meet one of the preconditions that the requester put on the request
Payload Too Large
The request is larger than the server is willing or able to process
URI Too Long
The URI provided was too long for the server to process
Unsupported Media Type
The request entity has a media type which the server or resource does not support
Range Not Satisfiable
The client has asked for a portion of the file, but the server cannot supply that portion
Expectation Failed
The server cannot meet the requirements of the Expect request-header field
I'm a teapot
This code was defined as an April Fools' joke and is not expected to be implemented by actual HTTP servers
Misdirected Request
The request was directed at a server that is not able to produce a response
Unprocessable Entity
The request was well-formed but was unable to be followed due to semantic errors
Locked
The resource that is being accessed is locked
Failed Dependency
The request failed because it depended on another request and that request failed
Too Early
The server is unwilling to risk processing a request that might be replayed
Upgrade Required
The client should switch to a different protocol
Precondition Required
The origin server requires the request to be conditional
Too Many Requests
The user has sent too many requests in a given amount of time
Request Header Fields Too Large
The server is unwilling to process the request because header fields are too large
Unavailable For Legal Reasons
The server is denying access to the resource as a consequence of a legal demand
5xx - Server Error
The server failed to fulfill an apparently valid request
Internal Server Error
A generic error message when an unexpected condition was encountered
Not Implemented
The server either does not recognize the request method, or it lacks the ability to fulfill it
Bad Gateway
The server was acting as a gateway or proxy and received an invalid response from upstream
Service Unavailable
The server is currently unavailable (because it is overloaded or down for maintenance)
Gateway Timeout
The server was acting as a gateway or proxy and did not receive a timely response from upstream
HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request
Variant Also Negotiates
Transparent content negotiation for the request results in a circular reference
Insufficient Storage
The server is unable to store the representation needed to complete the request
Loop Detected
The server detected an infinite loop while processing the request
Not Extended
Further extensions to the request are required for the server to fulfill it
Network Authentication Required
The client needs to authenticate to gain network access
Ferramentas Relacionadas
Sobre a Referência de Códigos de Status HTTP
Como Funciona
- Navegue pelos códigos de status HTTP organizados por categoria (1xx-5xx)
- Pesquise códigos específicos por número, nome ou descrição
- Filtre por categorias de códigos de status para navegação focada
- Obtenha explicações detalhadas para cada código de status
Casos de Uso Comuns
- Desenvolvedores web depurando respostas HTTP
- Administradores de sistemas solucionando problemas de servidor
- Estudantes aprendendo sobre protocolo HTTP
- Referência rápida durante o desenvolvimento de APIs