Handytool
UtviklerGratisKjøres lokalt

HTTP status-kodeoppslag

Slå opp hvilken som helst HTTP-statuskode — 1xx gjennom 5xx — med en helt norsk beskrivelse.

Klasse
  • 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.

Hentet fra RFC 9110 og IANA HTTP-statusregister.

Om HTTP status-kodeoppslag

Handy tools HTTP statuskode-oppslag er en hurtigreferanse for hver HTTP-status fra 100 Fortsett til 511 Nettverksautentisering kreves. Søk etter kode (404), navn (Not Found) eller fragment av beskrivelsen; filtrer etter klasse (1xx informativ, 2xx suksess, 3xx omdirigering, 4xx klient-feil, 5xx server-feil). Hentet fra RFC 9110 og IANA HTTP status-registeret, inkludert WebDAV og andre utvidelser du vil se i virkelige API-svar.

Funksjoner i HTTP status-kodeoppslag

  • 01

    Søk etter kode eller betydning

    Skriv en kode, et navn eller en setning fra beskrivelsen — listen filtreres øyeblikkelig. Nyttig når du husker at 422 betyr "noe semantisk" men ikke kan huske det eksakte navnet.

  • 02

    Klassekfilter

    Innsnevre listen til en enkelt klasse — 4xx når du debugger en klient-feil, 5xx når du jager en server-bug, 3xx når du utglatter en omdirigeringskjede.

  • 03

    Helt norsk forklaring

    Hvert oppslag har en enlinjesammendrag rettet mot utviklere — hva koden faktisk betyr i praksis, ikke bare den formelle RFC-formuleringen.

Vanlige spørsmål om HTTP status-kodeoppslag

Hva er forskjellen mellom 401 og 403?
401 Uautorisert betyr at forespørselen mangler gyldig autentisering — logg inn og forsøk igjen. 403 Forbudt betyr at du er autentisert men ikke har lov til å få tilgang til ressursen — legitimasjon hjelper ikke.
Når skal jeg returnere 422 vs 400?
400 Dårlig forespørsel er for dårlig dannet syntaks (brukket JSON, manglende nødvendig felt). 422 Ubehandlet enhetsvar er for syntaktisk gyldige forespørsler som mislykkes forretningsvalidering (e-post finnes allerede, alder må være ≥ 18).
Er 418 Jeg er en tekande en ekte statuskode?
Ja — definert som en aprilsnarr i RFC 2324 (1998) og bekreftet på nytt i RFC 7168. Den brukes ikke av HTTP selv, men vises i IANA-registeret, og en håndfull tjenester returnerer det som et påskeegg.
Hva skjer etter 5xx-koder over 511?
Koder over 511 er ikke tildelt i IANA-registeret. Du kan se tilpassede 5xx-koder fra spesifikke plattformer (Cloudflare bruker 520-527 for oppstrøms-problemer), men de er leverandørspesifikke utvidelser, ikke standard HTTP.

Relaterte verktøy

Utvikler →

Utforsk flere verktøy

Alle verktøy →