Catégorie: Développement
Recherche de codes de statut HTTP
Recherchez tous les codes de statut HTTP et leur signification
Parcourez l'ensemble des codes de statut HTTP — de 1xx à 5xx — par numéro, nom ou mot-clé, et lisez une explication courte et concrète de ce que signifie chacun. Fonctionne entièrement dans votre navigateur à partir d'une table de référence intégrée.
62 codes
| Code | Nom | Catégorie | Signification |
|---|---|---|---|
| 100 | Continue | 1xx Information | The initial part of the request was received; the client should continue. |
| 101 | Switching Protocols | 1xx Information | The server is switching protocols as requested by Upgrade. |
| 102 | Processing | 1xx Information | The server has received the request and is still processing it. |
| 103 | Early Hints | 1xx Information | Preload or preconnect hints sent before the final response. |
| 200 | OK | 2xx Succès | The request succeeded. |
| 201 | Created | 2xx Succès | The request succeeded and a new resource was created. |
| 202 | Accepted | 2xx Succès | The request was accepted for processing but is not complete. |
| 203 | Non-Authoritative Information | 2xx Succès | The payload was transformed by a proxy from the origin response. |
| 204 | No Content | 2xx Succès | The request succeeded but there is no content to send. |
| 205 | Reset Content | 2xx Succès | The client should reset the document view that sent the request. |
| 206 | Partial Content | 2xx Succès | Only part of the resource is being sent, per a Range header. |
| 207 | Multi-Status | 2xx Succès | A WebDAV response conveying status for multiple sub-requests. |
| 208 | Already Reported | 2xx Succès | A WebDAV binding was already enumerated in a previous reply. |
| 226 | IM Used | 2xx Succès | The server fulfilled the request using instance manipulations. |
| 300 | Multiple Choices | 3xx Redirection | The request has more than one possible response. |
| 301 | Moved Permanently | 3xx Redirection | The resource has been permanently moved to a new URL. |
| 302 | Found | 3xx Redirection | The resource is temporarily at a different URL. |
| 303 | See Other | 3xx Redirection | The response can be found under a different URL using GET. |
| 304 | Not Modified | 3xx Redirection | The resource has not changed since the last request; use the cache. |
| 305 | Use Proxy | 3xx Redirection | Deprecated: the requested resource must be accessed through a proxy. |
| 307 | Temporary Redirect | 3xx Redirection | The resource is temporarily at a different URL; method must not change. |
| 308 | Permanent Redirect | 3xx Redirection | The resource has permanently moved; method must not change. |
| 400 | Bad Request | 4xx Erreur client | The server cannot process the request due to a client error. |
| 401 | Unauthorized | 4xx Erreur client | Authentication is required and has failed or not been provided. |
| 402 | Payment Required | 4xx Erreur client | Reserved for future use. |
| 403 | Forbidden | 4xx Erreur client | The server understood the request but refuses to authorize it. |
| 404 | Not Found | 4xx Erreur client | The server can not find the requested resource. |
| 405 | Method Not Allowed | 4xx Erreur client | The request method is not supported for this resource. |
| 406 | Not Acceptable | 4xx Erreur client | No content matching the Accept headers was found. |
| 407 | Proxy Authentication Required | 4xx Erreur client | The client must authenticate with the proxy first. |
| 408 | Request Timeout | 4xx Erreur client | The server timed out waiting for the request. |
| 409 | Conflict | 4xx Erreur client | The request conflicts with the current state of the resource. |
| 410 | Gone | 4xx Erreur client | The resource is no longer available and will not come back. |
| 411 | Length Required | 4xx Erreur client | The request did not specify the length of its content. |
| 412 | Precondition Failed | 4xx Erreur client | A precondition in the request headers was not met. |
| 413 | Payload Too Large | 4xx Erreur client | The request entity is larger than the server can handle. |
| 414 | URI Too Long | 4xx Erreur client | The requested URI is longer than the server can interpret. |
| 415 | Unsupported Media Type | 4xx Erreur client | The media format of the request is not supported. |
| 416 | Range Not Satisfiable | 4xx Erreur client | The requested range cannot be satisfied. |
| 417 | Expectation Failed | 4xx Erreur client | The Expect header could not be met by the server. |
| 418 | I'm a Teapot | 4xx Erreur client | An April Fools' joke status code from RFC 2324. |
| 421 | Misdirected Request | 4xx Erreur client | The request was directed at a server unable to produce a response. |
| 422 | Unprocessable Entity | 4xx Erreur client | The request was well-formed but semantically incorrect. |
| 423 | Locked | 4xx Erreur client | The resource that is being accessed is locked. |
| 424 | Failed Dependency | 4xx Erreur client | The request failed because a prior dependent request failed. |
| 425 | Too Early | 4xx Erreur client | The server is unwilling to risk processing a replayable request. |
| 426 | Upgrade Required | 4xx Erreur client | The client should switch to a different protocol. |
| 428 | Precondition Required | 4xx Erreur client | The origin server requires the request to be conditional. |
| 429 | Too Many Requests | 4xx Erreur client | The client has sent too many requests in a given time. |
| 431 | Request Header Fields Too Large | 4xx Erreur client | The header fields are too large for the server. |
| 451 | Unavailable For Legal Reasons | 4xx Erreur client | The resource is unavailable for legal reasons. |
| 500 | Internal Server Error | 5xx Erreur serveur | The server encountered an unexpected condition. |
| 501 | Not Implemented | 5xx Erreur serveur | The server does not support the functionality required. |
| 502 | Bad Gateway | 5xx Erreur serveur | The server, acting as a gateway, got an invalid response. |
| 503 | Service Unavailable | 5xx Erreur serveur | The server is not ready to handle the request. |
| 504 | Gateway Timeout | 5xx Erreur serveur | The server, acting as a gateway, did not get a response in time. |
| 505 | HTTP Version Not Supported | 5xx Erreur serveur | The HTTP version used in the request is not supported. |
| 506 | Variant Also Negotiates | 5xx Erreur serveur | Transparent content negotiation resulted in a circular reference. |
| 507 | Insufficient Storage | 5xx Erreur serveur | The server is unable to store the representation needed. |
| 508 | Loop Detected | 5xx Erreur serveur | The server detected an infinite loop while processing the request. |
| 510 | Not Extended | 5xx Erreur serveur | Further extensions to the request are required. |
| 511 | Network Authentication Required | 5xx Erreur serveur | The client needs to authenticate to gain network access. |
Tout sur cette page est traité dans votre navigateur. Rien n'est envoyé.
À quoi sert cet outil
Chaque réponse HTTP porte un code à trois chiffres qui indique au client ce qui s'est passé : 2xx pour un succès, 3xx pour une redirection, 4xx pour une erreur côté client, 5xx pour une défaillance côté serveur. Cet outil rassemble les codes enregistrés auprès de l'IANA avec une description en langage clair, afin que vous puissiez vérifier le sens d'un code ou trouver le bon à renvoyer sans quitter votre éditeur.
Mode d'emploi
- Saisissez un code de statut, son nom, ou un mot-clé comme « rate limit ».
- Restreignez éventuellement les résultats à une seule catégorie (1xx–5xx).
- Lisez l'explication courte associée au code correspondant.
Confidentialité
Cet outil fonctionne entièrement dans votre navigateur. Ce que vous saisissez n'est jamais envoyé, stocké ni partagé : fermer l'onglet suffit à tout effacer.
Questions fréquentes
- D'où vient cette liste ?
- D'une table locale des codes enregistrés auprès de l'IANA, couvrant tous les codes qu'une API web ou une interaction navigateur classique peut renvoyer. Elle n'effectue aucun appel à un serveur.
- Quelle est la différence entre 401 et 403 ?
- 401 Unauthorized signifie que la requête nécessite des identifiants d'authentification valides ; 403 Forbidden signifie que le serveur sait qui vous êtes mais refuse quand même d'autoriser l'action.
- Pourquoi le code 418 existe-t-il ?
- « I'm a Teapot » provient d'une RFC humoristique du 1er avril 1998. Il est rarement utilisé sérieusement, même si certaines API l'emploient comme clin d'œil.