Kode Status HTTP

Cari kode status HTTP mana pun — berdasarkan nomor (mis. 422), kelas (mis. 4xx), atau nama (mis. "gateway"). Semuanya berjalan di browser Anda.

• 100ContinueInformational

  The client should continue the request or ignore this response if already finished.

• 101Switching ProtocolsInformational

  The server is switching protocols as requested by the client (e.g. to WebSocket).

• 102ProcessingInformational

  The server has received and is processing the request, but no response is available yet (WebDAV).

• 103Early HintsInformational

  Used to return some response headers (e.g. preload links) before the final response.

• 200OKSuccess

  The request succeeded. The meaning depends on the HTTP method used.

• 201CreatedSuccess

  The request succeeded and a new resource was created as a result.

• 202AcceptedSuccess

  The request has been received but not yet acted upon — processing is asynchronous.

• 203Non-Authoritative InformationSuccess

  The returned metadata is from a copy or a third party, not the origin server.

• 204No ContentSuccess

  The request succeeded but there is no content to send in the response body.

• 205Reset ContentSuccess

  Tells the client to reset the document that sent the request (e.g. clear a form).

• 206Partial ContentSuccess

  The server is delivering only part of the resource in response to a Range header.

• 207Multi-StatusSuccess

  Conveys information about multiple resources for WebDAV requests.

• 208Already ReportedSuccess

  Members of a WebDAV binding have already been enumerated and are not included again.

• 226IM UsedSuccess

  The server fulfilled a GET request; the response represents one or more instance-manipulations.

• 300Multiple ChoicesRedirection

  The request has more than one possible response; the client should choose one.

• 301Moved PermanentlyRedirection

  The resource has a new permanent URL, given by the Location header.

• 302FoundRedirection

  The resource is temporarily at a different URL; keep using the original URL for future requests.

• 303See OtherRedirection

  The client should GET the resource at another URL, typically after a POST.

• 304Not ModifiedRedirection

  The cached version is still valid; the client can reuse it (conditional GET).

• 307Temporary RedirectRedirection

  Like 302, but the method and body must not change when redirecting.

• 308Permanent RedirectRedirection

  Like 301, but the method and body must not change when redirecting.

• 400Bad RequestClient Error

  The server cannot process the request due to a client error (malformed syntax, invalid framing).

• 401UnauthorizedClient Error

  Authentication is required and has failed or not yet been provided.

• 402Payment RequiredClient Error

  Reserved for future use; sometimes used by APIs for billing/quota limits.

• 403ForbiddenClient Error

  The server understood the request but refuses to authorize it.

• 404Not FoundClient Error

  The server cannot find the requested resource. The URL is unrecognised.

• 405Method Not AllowedClient Error

  The request method is known but not supported by the target resource.

• 406Not AcceptableClient Error

  The resource cannot produce a response matching the Accept headers.

• 407Proxy Authentication RequiredClient Error

  Authentication with a proxy is required before the request can proceed.

• 408Request TimeoutClient Error

  The server timed out waiting for the request. The client may repeat it.

• 409ConflictClient Error

  The request conflicts with the current state of the resource (e.g. edit conflict).

• 410GoneClient Error

  The resource is permanently gone with no forwarding address.

• 411Length RequiredClient Error

  The server requires a Content-Length header, which was not provided.

• 412Precondition FailedClient Error

  A precondition in the request headers (e.g. If-Match) was not met.

• 413Payload Too LargeClient Error

  The request body is larger than the server is willing or able to process.

• 414URI Too LongClient Error

  The request URI is longer than the server is willing to interpret.

• 415Unsupported Media TypeClient Error

  The request body is in a format the server does not support.

• 416Range Not SatisfiableClient Error

  The Range specified cannot be fulfilled — it may lie outside the resource size.

• 417Expectation FailedClient Error

  The expectation in the Expect request header could not be met.

• 418I'm a teapotClient Error

  An April Fools joke from RFC 2324 — the server refuses to brew coffee in a teapot.

• 421Misdirected RequestClient Error

  The request was directed at a server unable to produce a response for it.

• 422Unprocessable EntityClient Error

  The request was well-formed but has semantic errors and cannot be processed (common for validation).

• 423LockedClient Error

  The resource being accessed is locked (WebDAV).

• 424Failed DependencyClient Error

  The request failed because it depended on another request that failed (WebDAV).

• 425Too EarlyClient Error

  The server is unwilling to process a request that might be replayed.

• 426Upgrade RequiredClient Error

  The client should switch to a different protocol given in the Upgrade header.

• 428Precondition RequiredClient Error

  The origin server requires the request to be conditional to avoid lost updates.

• 429Too Many RequestsClient Error

  The client has sent too many requests in a given time (rate limiting).

• 431Request Header Fields Too LargeClient Error

  The header fields are too large for the server to process.

• 451Unavailable For Legal ReasonsClient Error

  The resource is unavailable due to legal demands (e.g. censorship).

• 500Internal Server ErrorServer Error

  The server hit an unexpected condition that prevented it from fulfilling the request.

• 501Not ImplementedServer Error

  The server does not support the functionality required to fulfil the request.

• 502Bad GatewayServer Error

  The server, acting as a gateway, got an invalid response from the upstream server.

• 503Service UnavailableServer Error

  The server is not ready — it may be overloaded or down for maintenance.

• 504Gateway TimeoutServer Error

  The server, acting as a gateway, did not get a timely response from the upstream server.

• 505HTTP Version Not SupportedServer Error

  The HTTP version used in the request is not supported by the server.

• 506Variant Also NegotiatesServer Error

  A content-negotiation configuration error on the server.

• 507Insufficient StorageServer Error

  The server cannot store the representation needed to complete the request (WebDAV).

• 508Loop DetectedServer Error

  The server detected an infinite loop while processing the request (WebDAV).

• 510Not ExtendedServer Error

  Further extensions to the request are required for the server to fulfil it.

• 511Network Authentication RequiredServer Error

  The client needs to authenticate to gain network access (e.g. a captive portal).