Handytool
PengembangGratisBerjalan secara lokal

Pencarian kode status HTTP

Cari kode status HTTP apa pun — 1xx melalui 5xx — dengan deskripsi bahasa Inggris biasa.

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

Bersumber dari RFC 9110 dan daftar status HTTP IANA.

Tentang Pencarian kode status HTTP

Pencarian kode status HTTP Handytool adalah referensi cepat untuk setiap status HTTP dari 100 Continue hingga 511 Network Authentication Required. Cari berdasarkan kode (404), nama (Not Found), atau fragmen deskripsi; filter berdasarkan kelas (1xx informatif, 2xx sukses, 3xx pengalihan, 4xx kesalahan klien, 5xx kesalahan server). Bersumber dari RFC 9110 dan daftar status HTTP IANA, termasuk WebDAV dan ekstensi lainnya yang akan Anda lihat dalam respons API dunia nyata.

Fitur Pencarian kode status HTTP

  • 01

    Cari berdasarkan kode atau arti

    Ketik kode, nama, atau frasa dari deskripsi — daftar filter secara instan. Berguna ketika Anda ingat 422 berarti "sesuatu semantik" tetapi tidak dapat mengingat nama pastinya.

  • 02

    Filter kelas

    Perkecil daftar ke kelas tunggal — 4xx saat Anda men-debug kesalahan klien, 5xx saat Anda mengejar bug server, 3xx saat Anda membongkar rantai pengalihan.

  • 03

    Penjelasan bahasa Inggris biasa

    Setiap entri memiliki ringkasan satu kalimat yang ditujukan pada pengembang — apa yang benar-benar dilakukan kode dalam praktik, bukan hanya kata resmi RFC.

FAQ Pencarian kode status HTTP

Apa perbedaan antara 401 dan 403?
401 Unauthorized berarti permintaan kekurangan autentikasi yang valid — masuk dan coba lagi. 403 Forbidden berarti Anda diautentikasi tetapi tidak diizinkan mengakses sumber daya — kredensial tidak akan membantu.
Kapan saya harus mengembalikan 422 vs 400?
400 Bad Request untuk sintaks yang tidak terbentuk (JSON rusak, field wajib hilang). 422 Unprocessable Entity untuk permintaan yang valid secara sintaks tetapi gagal validasi bisnis (email sudah ada, usia harus ≥ 18).
Apakah 418 I'm a teapot adalah kode status nyata?
Ya — didefinisikan sebagai lelucon April Fools' di RFC 2324 (1998) dan dikonfirmasi kembali di RFC 7168. Tidak digunakan oleh HTTP itu sendiri tetapi muncul dalam daftar IANA, dan segelintir layanan mengembalikannya sebagai Easter egg.
Apa yang terjadi setelah kode 5xx di atas 511?
Kode di atas 511 tidak ditugaskan dalam daftar IANA. Anda mungkin melihat kode 5xx khusus dari platform tertentu (Cloudflare menggunakan 520-527 untuk masalah upstream), tetapi itu adalah ekstensi khusus vendor, bukan HTTP standar.

Alat terkait

Pengembang →

Jelajahi alat lain

Semua alat →