Continue
Initial part of a request was received and the client should continue with it.
Codes HTTP
Référence cherchable des codes de statut HTTP avec descriptions et références aux RFCs.
62 affichés
1xxInformational · 4
RFC 9110
Switching Protocols
Server agrees to switch protocols based on the Upgrade header.
Processing
Server has accepted the request but is still processing it (WebDAV).
Early Hints
Send preliminary headers (Link, etc.) before the final response.
2xxSuccess · 10
OK
Request succeeded.
Created
Request succeeded and a new resource was created.
Accepted
Request was accepted for processing but has not yet completed.
Non-Authoritative Information
Returned metainformation differs from the origin server's response.
No Content
Request succeeded; no body to return.
Reset Content
Request succeeded; the client should reset the document view.
Partial Content
Range request succeeded.
Multi-Status
Body is an XML message with status for multiple resources (WebDAV).
Already Reported
Members of a WebDAV binding were already enumerated.
IM Used
Server fulfilled a GET request and the response is a representation of one or more instance manipulations.
3xxRedirection · 8
Multiple Choices
Multiple representations are available; the client may choose.
Moved Permanently
Resource has a new permanent URI.
Found
Resource is temporarily under a different URI.
See Other
Response is found under a different URI; client should GET it.
Not Modified
Conditional GET: the cached representation is still fresh.
Use Proxy
Deprecated. Resource must be accessed through a proxy.
Temporary Redirect
Resource is temporarily under a different URI; method must not change.
Permanent Redirect
Resource has a new permanent URI; method must not change.
4xxClient error · 29
Bad Request
Server cannot or will not process the request due to a client error.
Unauthorized
Authentication is required and has failed or has not been provided.
Payment Required
Reserved for future use.
Forbidden
Server understood the request but refuses to authorize it.
Not Found
Server can't find the requested resource.
Method Not Allowed
Method is known but not supported by the target resource.
Not Acceptable
Resource cannot generate content matching the Accept headers.
Proxy Authentication Required
Client must authenticate with a proxy first.
Request Timeout
Server timed out waiting for the client.
Conflict
Request conflicts with the current state of the resource.
Gone
Resource is permanently unavailable.
Length Required
Server requires the Content-Length header.
Precondition Failed
Precondition in request headers failed.
Content Too Large
Request body is larger than the server is willing to process.
URI Too Long
Request URI is longer than the server is willing to interpret.
Unsupported Media Type
Request body is in a format the server doesn't support.
Range Not Satisfiable
None of the ranges in the Range header overlap the resource.
Expectation Failed
Expectation in the Expect header could not be met.
I'm a teapot
Server is a teapot. April Fools' joke from RFC 2324; widely implemented as an Easter egg.
Misdirected Request
Request was directed to a server unable to produce a response.
Unprocessable Content
Request is well-formed but semantically invalid.
Locked
Resource is locked (WebDAV).
Failed Dependency
Request failed because of a previous request (WebDAV).
Too Early
Server is unwilling to risk processing a request that might be replayed.
Upgrade Required
Client must switch to a different protocol.
Precondition Required
Server requires the request to be conditional.
Too Many Requests
Client has sent too many requests in a given time (rate limited).
Request Header Fields Too Large
One or more request headers (or all of them) are too large.
Unavailable For Legal Reasons
Resource is unavailable due to legal demands.
5xxServer error · 11
Internal Server Error
Server encountered an unexpected condition.
Not Implemented
Server does not support the functionality required.
Bad Gateway
Server, while acting as a gateway, got an invalid response from upstream.
Service Unavailable
Server is currently unable to handle the request (overloaded or down).
Gateway Timeout
Server, while acting as a gateway, didn't get a response in time.
HTTP Version Not Supported
Server doesn't support the HTTP version in the request.
Variant Also Negotiates
Transparent content negotiation results in a circular reference.
Insufficient Storage
Server cannot store the representation needed to complete the request (WebDAV).
Loop Detected
Server detected an infinite loop while processing (WebDAV).
Not Extended
Further extensions to the request are required.
Network Authentication Required
Client needs to authenticate to gain network access (captive portal).
Les entrées restent sur cet appareil. Chaque outil dev de TaskKit tourne entièrement dans ton navigateur. Tokens, payloads et texte collé ne sont pas transmis aux serveurs de TaskKit ni à des tiers.
Ce que fait cet outil
Une référence cherchable pour chaque code de statut HTTP standard, organisée par classe (1xx informationnel, 2xx succès, 3xx redirection, 4xx erreur client, 5xx erreur serveur). Cherche par numéro, par nom ou par description. Chaque entrée inclut la phrase de raison canonique et le RFC où elle est définie.
Quand l'utiliser
- Décider entre
401 Unauthorizedet403 Forbiddenpour une requête refusée. - Confirmer si une redirection devrait être
302,303,307ou308. - Chercher un code inhabituel qui vient d'apparaître dans une ligne de log.
- Vérifier quel RFC a introduit un code (par exemple,
451 Unavailable For Legal Reasonsest dans le RFC 7725).
Comment ça marche
Le dataset est statique et embarqué dans le bundle de la page. Pas d'appel d'API — la recherche tourne contre un index en mémoire, donc c'est instantané même sur des connexions lentes. Les métadonnées de chaque code viennent directement du Registre IANA HTTP Status Code et des RFCs pertinents (surtout 9110, avec les codes plus anciens encore pointant vers 7231 et plus tôt).
Notes
401 vs 403 ? 401 veut dire « tu n'as pas prouvé qui tu es — réessaie avec des credentials. » 403 veut dire « je sais qui tu es et tu ne peux pas avoir ça. » Si l'utilisateur en se connectant changerait la réponse, renvoie 401 ; sinon, renvoie 403.
302 vs 307 ? 302 était originellement censé préserver la méthode de la requête à la redirection, mais la plupart des navigateurs ont historiquement réécrit POST en GET. 303 et 307 ont été ajoutés pour rendre l'intention explicite : 303 See Other GET toujours la nouvelle URL, 307 Temporary Redirect préserve toujours la méthode. Utilise 303 après un POST réussi, 307 pour une redirection temporaire qui préserve la méthode.
418 I'm a teapot est réel ? Oui, et c'est encore dans le RFC 2324 (1er avril 1998) et reconnu dans le RFC 9110 §15.5.19. À utiliser avec parcimonie.
Outils liés
- cURL ↔ fetch — rejoue des requêtes pour voir les codes en direct
- Formateur JSON — pour inspecter les corps de réponse