Handytool
SviluppatoreGratisEseguito localmente

Ricerca di codici di stato HTTP

Cerca qualsiasi codice di stato HTTP — 1xx a 5xx — con una descrizione in linguaggio naturale.

Classe
  • 100Continue

    Server received the request headers; client should send the body.

  • 101Switching Protocols

    The server is switching protocols as requested by the client.

  • 102Processing

    Request received but not yet processed (WebDAV).

  • 103Early Hints

    Used to return some response headers before final HTTP message.

  • 200OK

    Standard success response.

  • 201Created

    Request succeeded and a new resource was created.

  • 202Accepted

    Request accepted for processing but not completed.

  • 203Non-Authoritative Information

    Returned metadata is from a third-party copy.

  • 204No Content

    Request succeeded but no content is returned.

  • 205Reset Content

    Request succeeded; client should reset the document view.

  • 206Partial Content

    Range request succeeded; partial content returned.

  • 207Multi-Status

    Body contains multiple statuses (WebDAV).

  • 208Already Reported

    Members of a DAV binding already enumerated.

  • 226IM Used

    Server fulfilled a GET request and the response is the result of one or more instance-manipulations.

  • 300Multiple Choices

    Request has more than one possible response.

  • 301Moved Permanently

    Resource moved to a new permanent URL.

  • 302Found

    Resource is temporarily at a different URL.

  • 303See Other

    Client should follow the response to a new URL with GET.

  • 304Not Modified

    Cached version is still valid; no body returned.

  • 307Temporary Redirect

    Same method should be used at the new URL.

  • 308Permanent Redirect

    Same as 301 but the request method must not change.

  • 400Bad Request

    Server cannot or will not process due to a client error.

  • 401Unauthorized

    Authentication required and has failed or not been provided.

  • 402Payment Required

    Reserved for future use, sometimes used for paywalls.

  • 403Forbidden

    Server understood but refuses to authorize.

  • 404Not Found

    The requested resource could not be found.

  • 405Method Not Allowed

    Request method is known but not supported by the resource.

  • 406Not Acceptable

    Resource cannot produce content matching the Accept headers.

  • 407Proxy Authentication Required

    Client must authenticate with the proxy.

  • 408Request Timeout

    Server timed out waiting for the request.

  • 409Conflict

    Request conflicts with the current state of the resource.

  • 410Gone

    Resource is no longer available and will not be available again.

  • 411Length Required

    Content-Length header is required.

  • 412Precondition Failed

    A precondition in the request headers was not met.

  • 413Payload Too Large

    Request entity is larger than the server is willing to process.

  • 414URI Too Long

    URI is longer than the server is willing to interpret.

  • 415Unsupported Media Type

    Media format of the request is not supported.

  • 416Range Not Satisfiable

    Requested range cannot be served.

  • 417Expectation Failed

    Expectation in Expect header could not be met.

  • 418I'm a teapot

    Server refuses to brew coffee because it is, permanently, a teapot.

  • 421Misdirected Request

    Request was directed to a server unable to produce a response.

  • 422Unprocessable Entity

    Request was well-formed but had semantic errors.

  • 423Locked

    Resource is locked (WebDAV).

  • 424Failed Dependency

    Request failed because of a previous failed request (WebDAV).

  • 425Too Early

    Server unwilling to risk processing a replay-vulnerable request.

  • 426Upgrade Required

    Client must upgrade to a different protocol.

  • 428Precondition Required

    Server requires the request to be conditional.

  • 429Too Many Requests

    Client has sent too many requests in a given amount of time.

  • 431Request Header Fields Too Large

    Headers are too large for the server to process.

  • 451Unavailable For Legal Reasons

    Resource cannot be served for legal reasons.

  • 500Internal Server Error

    Generic server error response.

  • 501Not Implemented

    Server does not support the request method.

  • 502Bad Gateway

    Server received an invalid response from an upstream server.

  • 503Service Unavailable

    Server is overloaded or down for maintenance.

  • 504Gateway Timeout

    Upstream server did not respond in time.

  • 505HTTP Version Not Supported

    HTTP version in the request is not supported.

  • 506Variant Also Negotiates

    Internal configuration error in transparent content negotiation.

  • 507Insufficient Storage

    Server is unable to store the representation (WebDAV).

  • 508Loop Detected

    Server detected an infinite loop while processing (WebDAV).

  • 510Not Extended

    Further extensions to the request are required.

  • 511Network Authentication Required

    Client needs to authenticate to gain network access.

Tratto da RFC 9110 e dal registro dei codici di stato HTTP IANA.

Informazioni su Ricerca di codici di stato HTTP

La ricerca di codici di stato HTTP di Handytool è un riferimento veloce per ogni stato HTTP da 100 Continue a 511 Network Authentication Required. Cerca per codice (404), nome (Not Found) o frammento della descrizione; filtra per classe (1xx informational, 2xx success, 3xx redirect, 4xx client error, 5xx server error). Sourced from RFC 9110 e il registro di stato IANA HTTP, inclusi WebDAV e altre estensioni che vedrai nelle risposte API del mondo reale.

Funzionalità di Ricerca di codici di stato HTTP

  • 01

    Cerca per codice o significato

    Digita un codice, un nome o una frase dalla descrizione — l'elenco filtra istantaneamente. Utile quando ricordi che 422 significa « qualcosa di semantico » ma non puoi ricordare il nome esatto.

  • 02

    Filtro di classe

    Restringi l'elenco a una sola classe — 4xx quando stai debugging un errore client, 5xx quando stai inseguendo un bug server, 3xx quando stai districando una catena di reindirizzamento.

  • 03

    Spiegazioni in linguaggio naturale

    Ogni voce ha un riassunto di una frase rivolto agli sviluppatori — cosa il codice significa effettivamente in pratica, non solo il linguaggio formale RFC.

Domande frequenti su Ricerca di codici di stato HTTP

Qual è la differenza tra 401 e 403?
401 Unauthorized significa che la richiesta manca di un'autenticazione valida — accedi e riprova. 403 Forbidden significa che sei autenticato ma non ti è consentito accedere alla risorsa — le credenziali non aiuteranno.
Quando dovrei restituire 422 vs 400?
400 Bad Request è per la sintassi malformata (JSON rotto, campo richiesto mancante). 422 Unprocessable Entity è per richieste sintatticamente valide che non superano la validazione del business (l'email esiste già, l'età deve essere ≥ 18).
È 418 I'm a teapot un vero codice di stato?
Sì — definito come uno scherzo di April Fools' in RFC 2324 (1998) e riaffermato in RFC 7168. Non è usato da HTTP stesso ma appare nel registro IANA e una manciata di servizi lo restituisce come un Easter egg.
Cosa succede dopo i codici 5xx sopra 511?
I codici sopra 511 non sono assegnati nel registro IANA. Potresti vedere codici 5xx personalizzati da piattaforme specifiche (Cloudflare utilizza 520-527 per i problemi upstream), ma sono estensioni specifiche del fornitore, non HTTP standard.

Strumenti correlati

Sviluppatore →

Esplora altri strumenti

Tutti gli strumenti →