Continue
Initial part of a request was received and the client should continue with it.
Kode Status HTTP
Referensi kode status HTTP yang dapat dicari dengan deskripsi dan referensi RFC.
62 ditampilkan
1xxInformational · 4
RFC 9110
Switching Protocols
Server agrees to switch protocols based on the Upgrade header.
Processing
Server has accepted the request but is still processing it (WebDAV).
Early Hints
Send preliminary headers (Link, etc.) before the final response.
2xxSuccess · 10
OK
Request succeeded.
Created
Request succeeded and a new resource was created.
Accepted
Request was accepted for processing but has not yet completed.
Non-Authoritative Information
Returned metainformation differs from the origin server's response.
No Content
Request succeeded; no body to return.
Reset Content
Request succeeded; the client should reset the document view.
Partial Content
Range request succeeded.
Multi-Status
Body is an XML message with status for multiple resources (WebDAV).
Already Reported
Members of a WebDAV binding were already enumerated.
IM Used
Server fulfilled a GET request and the response is a representation of one or more instance manipulations.
3xxRedirection · 8
Multiple Choices
Multiple representations are available; the client may choose.
Moved Permanently
Resource has a new permanent URI.
Found
Resource is temporarily under a different URI.
See Other
Response is found under a different URI; client should GET it.
Not Modified
Conditional GET: the cached representation is still fresh.
Use Proxy
Deprecated. Resource must be accessed through a proxy.
Temporary Redirect
Resource is temporarily under a different URI; method must not change.
Permanent Redirect
Resource has a new permanent URI; method must not change.
4xxClient error · 29
Bad Request
Server cannot or will not process the request due to a client error.
Unauthorized
Authentication is required and has failed or has not been provided.
Payment Required
Reserved for future use.
Forbidden
Server understood the request but refuses to authorize it.
Not Found
Server can't find the requested resource.
Method Not Allowed
Method is known but not supported by the target resource.
Not Acceptable
Resource cannot generate content matching the Accept headers.
Proxy Authentication Required
Client must authenticate with a proxy first.
Request Timeout
Server timed out waiting for the client.
Conflict
Request conflicts with the current state of the resource.
Gone
Resource is permanently unavailable.
Length Required
Server requires the Content-Length header.
Precondition Failed
Precondition in request headers failed.
Content Too Large
Request body is larger than the server is willing to process.
URI Too Long
Request URI is longer than the server is willing to interpret.
Unsupported Media Type
Request body is in a format the server doesn't support.
Range Not Satisfiable
None of the ranges in the Range header overlap the resource.
Expectation Failed
Expectation in the Expect header could not be met.
I'm a teapot
Server is a teapot. April Fools' joke from RFC 2324; widely implemented as an Easter egg.
Misdirected Request
Request was directed to a server unable to produce a response.
Unprocessable Content
Request is well-formed but semantically invalid.
Locked
Resource is locked (WebDAV).
Failed Dependency
Request failed because of a previous request (WebDAV).
Too Early
Server is unwilling to risk processing a request that might be replayed.
Upgrade Required
Client must switch to a different protocol.
Precondition Required
Server requires the request to be conditional.
Too Many Requests
Client has sent too many requests in a given time (rate limited).
Request Header Fields Too Large
One or more request headers (or all of them) are too large.
Unavailable For Legal Reasons
Resource is unavailable due to legal demands.
5xxServer error · 11
Internal Server Error
Server encountered an unexpected condition.
Not Implemented
Server does not support the functionality required.
Bad Gateway
Server, while acting as a gateway, got an invalid response from upstream.
Service Unavailable
Server is currently unable to handle the request (overloaded or down).
Gateway Timeout
Server, while acting as a gateway, didn't get a response in time.
HTTP Version Not Supported
Server doesn't support the HTTP version in the request.
Variant Also Negotiates
Transparent content negotiation results in a circular reference.
Insufficient Storage
Server cannot store the representation needed to complete the request (WebDAV).
Loop Detected
Server detected an infinite loop while processing (WebDAV).
Not Extended
Further extensions to the request are required.
Network Authentication Required
Client needs to authenticate to gain network access (captive portal).
Input tetap di perangkat ini. Setiap tool developer di TaskKit berjalan sepenuhnya di browser kamu. Token, payload, dan teks yang di-paste tidak ditransmisikan ke server TaskKit atau pihak ketiga.
Apa yang dilakukan tool ini
Referensi yang dapat dicari untuk setiap kode status HTTP standar, diorganisasi berdasarkan kelas (1xx informasional, 2xx sukses, 3xx redirect, 4xx error client, 5xx error server). Cari berdasarkan nomor, berdasarkan nama, atau berdasarkan deskripsi. Setiap entri menyertakan reason phrase kanonis dan RFC tempat itu didefinisikan.
Kapan menggunakannya
- Memutuskan antara
401 Unauthorizeddan403 Forbiddenuntuk request yang ditolak. - Mengkonfirmasi apakah redirect harus
302,303,307, atau308. - Mencari kode tidak familiar yang baru muncul di baris log.
- Memeriksa RFC mana yang memperkenalkan kode (mis.
451 Unavailable For Legal Reasonsdi RFC 7725).
Cara kerjanya
Dataset adalah static dan dikirimkan di bundle halaman. Tidak ada panggilan API — pencarian berjalan terhadap indeks in-memory, jadi instan bahkan di koneksi lambat. Metadata setiap kode datang langsung dari Registry Kode Status HTTP IANA dan RFC yang relevan (sebagian besar 9110, dengan kode lebih tua masih menunjuk ke 7231 dan sebelumnya).
Catatan
401 vs. 403? 401 berarti « kamu tidak membuktikan siapa kamu — coba lagi dengan credential. » 403 berarti « saya tahu siapa kamu dan kamu tidak boleh memiliki ini. » Jika user yang login akan mengubah jawabannya, kembalikan 401; jika tidak, kembalikan 403.
302 vs. 307? 302 awalnya dimaksudkan untuk mempertahankan method request pada redirect, tapi sebagian besar browser secara historis menulis ulang POST ke GET. 303 dan 307 ditambahkan untuk membuat intent eksplisit: 303 See Other selalu GET URL baru, 307 Temporary Redirect selalu mempertahankan method. Gunakan 303 setelah POST yang sukses, 307 untuk redirect sementara yang mempertahankan method.
Apakah 418 I'm a teapot nyata? Ya, dan itu masih ada di RFC 2324 (1 April 1998) dan diakui di RFC 9110 §15.5.19. Gunakan dengan hemat.
Tools terkait
- cURL ↔ fetch — putar ulang request untuk melihat kode secara live
- Formatter JSON — untuk menginspeksi body respons