• Daftar Kode Status Respon HTTP

    Posted on 2 January 2013 by GmiB26.Net in Artikel.

    Anda yang berprofesi sebagai seorang admin web server, web developer atau bahkan admin jaringan yang terhubung dengan internet pasti tidak asing dengan code 200 OK, error 404 page not found atau 500 internal server error. Namun bagi anda yang masih belum menegtahuinya, anda akan bertanya-tanya apa maksud dari koe status dari website atau ip address yang anda akses tersebut. Berikut adalah daftar kode-kode status HTTP yang mungkin suatu ketika akan muncul saat anda mengakses sebuah website atau ip address tertentu.

    Daftar kode status HTML ini kami salin dari halaman Wikipedia bahasa inggris, jadi mohon maaf jika ada sebagian dari penjelasan kode yang tidak sesuai dalam penterjemahan atau bahkan tidak kami terjemahkan.

    Terdapat lima kelompok kode respon HTTP, dimana digit pertama dari setiap kode menyatakan salah satu dari kelima kelompok tersebut. Kode status HTTP didaftar dan disusun oleh  Internet Assigned Numbers Authority (IANA). Namun demikian, Microsoft IIS terkadang menggunakan desimal tambahan sub-kode untuk memberikan informasi yang lebih spesifik, tetapi ini tidak tercantum di sini.

    Kode informasi 1xx 

    Permintaan diterima, proses dilanjutkan.

    kelompok status kode ini menunjukkan respon sementara, hanya terdiri dari Line Status-dan header opsional, dan diakhiri oleh sebuah baris kosong. Karena HTTP/1.0 tidak mendefinisikan kode status 1xx, server tidak harus mengirim tanggapan 1xx ke klien HTTP/1.0 kecuali dalam kondisi eksperimental.

    100 Continue

    Ini berarti bahwa server telah menerima header permintaan, dan klien harus melanjutkan untuk mengirim request body (dalam kasus request body yang perlu dikirim, misalnya, POST request). Jika request body besar, pengiriman ke server ketika permintaan telah ditolak berdasarkan header yang tidak efisien. Agar server memeriksa apakah permintaan dapat diterima berdasarkan header permintaan itu saja, klien harus mengirimkan Expect: 100-continue sebagai header dalam permintaan awal dan memeriksa apakah kode status 100 Continue  diterima dalam respon sebelum melanjutkan (atau menerima 417 Expectation Failed dan tidak melanjutkan).

    101 Switching Protocols

    Ini berarti pemohon telah meminta server untuk beralih protokol dan server mengakui bahwa ia akan melakukannya. 

    102 Processing ( WebDAV , RFC 2518)

    Sebagian request WebDAV mungkin berisi banyak sub-permintaan yang melibatkan operasi file, mungkin diperlukan waktu yang lama untuk menyelesaikan permintaan.Kode ini menunjukkan bahwa server telah menerima dan memproses permintaan, tetapi respon belum tersedia. Hal ini untuk mencegah klien keluar dengan asumsi permintaan itu hilang.

    Kode Sukses 2xx

    kelompok kode status ini menunjukkan tindakan yang diminta oleh klien diterima, dipahami, diterima dan diproses dengan sukses.

    200 OK

    Standar respon untuk permintaan HTTP yang sukses. Respon yang sebenarnya akan tergantung pada metode yang digunakan dalam permintaan. Dalam permintaan GET, respon akan berisi entitas sesuai dengan sumber daya yang diminta. Dalam permintaan POST respon akan berisi entitas menggambarkan atau mengandung hasil dari tindakan. 

    201 Created

    Permintaan telah terpenuhi dan menghasilkan sumber daya baru yang diciptakan.

    202 Accepted

    Permintaan telah diterima untuk diproses, tetapi pengolahan belum selesai. Permintaan mungkin atau tidak mungkin pada akhirnya akan ditindaklanjuti, karena akan menjadi batasan saat proses sebenarnya terjadi.

    203 Non-Authoritative Information (since HTTP/1.1)

    Server berhasil memroses permintaan, tetapi mengembalikan informasi yang mungkin berasal dari sumber lain.

    204 No Content

    Server berhasil memroses permintaan, tetapi tidak mendapatkan konten apa pun.

    205 Reset Content

    Server berhasil memroses permintaan, tetapi tidak mendapatkan konten apa pun. Tidak seperti respon 204, respons ini mengharuskan pemohon mereset tampilan dokumen.

    206 Partial Content

    Server memberikan hanya sebagian dari sumber daya karena rentang header yang dikirimkan oleh klien. Rentang Header digunakan oleh alat-alat seperti wget untuk memungkinkan melanjutkan download terputus, atau membagi download ke bagian-bagian simultan.

    207 Multi-Status (WebDAV, RFC 4918)

    Isi pesan yang berikut adalah pesan XML Partial Content dan dapat berisi sejumlah kode respon terpisah, tergantung pada berapa banyak sub-permintaan dibuat.

    208 Sudah Dilaporkan (WebDAV, RFC 5842)

    Bagian dari DAV binding yang telah disebutkan sebelumnya dalam jawaban permintaan, dan tidak disertakan lagi.

    226 IM Digunakan (RFC 3229)

    Server telah memenuhi permintaan GET untuk sumber daya, dan respon adalah representasi dari hasil satu atau lebih contoh-manipulasi diterapkan pada contoh. 

    230 Otentikasi Sukses ( RFC 2.229 )

    Upaya otentikasi klien berhasil.

    Kode Redirection 3xx

    Klien harus mengambil tindakan tambahan untuk melengkapi permintaan tersebut.

    Kelompok kode status ini menunjukkan bahwa tindakan lebih lanjut perlu diambil oleh agen pengguna untuk memenuhi permintaan. Tindakan yang diperlukan dapat dilakukan oleh agen pengguna tanpa interaksi dengan pengguna jika dan hanya jika metode yang digunakan dalam permintaan kedua adalah GET atau HEAD. Seorang agen pengguna tidak seharusnya secara otomatis mengarahkan permintaan lebih dari lima kali, sejak pengalihan tersebut biasanya diidentifikasikan sebagai infinite loop.

    300 Multiple Choices

    Menunjukkan beberapa pilihan untuk sumber daya yang bisa klien ikuti. Ini, misalnya, dapat digunakan untuk menyajikan pilihan format yang berbeda untuk file daftar video, dengan berbagai ekstensi , atau disambiguasi kata.

    301 Moved Permanently

    Permintaan ini dan semua permintaan berikutnya harus diarahkan ke URI yang diberikan.

    302 Found

    Ini adalah contoh dari praktik industri yang bertentangan dengan standar. Spesifikasi HTTP/1.0 (RFC 1945) diperlukan klien untuk melakukan redirect sementara (ungkapan menggambarkan “Pindah sementara”), tetapi browser populer me-implementasikan 302 dengan fungsi dari 303. Oleh karena itu, HTTP/1.1 menambahkan kode status 303 dan 307 untuk membedakan antara dua perilaku. Namun, beberapa aplikasi Web dan kerangka menggunakan kode status 302 seolah-olah itu adalah 303.

    303 See Other (since HTTP/1.1)

    Respon terhadap permintaan tersebut dapat ditemukan di bawah URI yang lain menggunakan metode GET. Ketika menerima respon POST (atau PUT / DELETE), harus diasumsikan bahwa server telah menerima data dan redirect harus dikeluarkan dengan terpisah GET pesan.

    304 Not Modified

    Menunjukkan sumber daya belum diubah sejak diminta terakhir. 

    305 Use Proxy (since HTTP/1.1)

    Banyak klien HTTP (seperti Mozilla dan Internet Explorer ) tidak benar dalam menangani respon dengan kode status ini, terutama untuk alasan keamanan.

    306 Switch Proxy

    Tidak lagi digunakan.

    307 Temporary Redirect (since HTTP/1.1)

    Dalam hal ini, permintaan harus diulang dengan URI lain. Namun, permintaan berikutnya masih harus menggunakan URI asli

    308 Permanent Redirect (approved as experimental RFC)

    Permintaan, dan semua permintaan selanjutnya harus diulang dengan menggunakan URI lain. 307 dan 308 (seperti yang diusulkan) merupakan paralel dari 302 dan 301, tetapi tidak memungkinkan perubahan HTTP metode. Jadi, misalnya, mengirimkan formulir ke sumber daya yang dialihkan secara permanen bisa tetap lancar.

    To be continued… (masih capek gan mau lanjut terjemahin :D)

    Kode Klien Error 4xx

    The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. These status codes are applicable to any request method. User agents shoulddisplay any included entity to the user.

    400 Bad Request
    The request cannot be fulfilled due to bad syntax.
    401 Unauthorized
    Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource. See Basic access authentication and Digest access authentication.
    402 Payment Required
    Reserved for future use. The original intention was that this code might be used as part of some form of digital cash or micropayment scheme, but that has not happened, and this code is not usually used. As an example of its use, however, Apple’s MobileMe service generates a 402 error if the MobileMe account is delinquent. In addition, YouTube uses this status if a particular IP address has made excessive requests, and requires the person to enter a CAPTCHA.
    403 Forbidden
    The request was a valid request, but the server is refusing to respond to it.Unlike a 401 Unauthorized response, authenticating will make no difference. On servers where authentication is required, this commonly means that the provided credentials were successfully authenticated but that the credentials still do not grant the client permission to access the resource (e.g. a recognized user attempting to access restricted content).
    404 Not Found
    The requested resource could not be found but may be available again in the future.] Subsequent requests by the client are permissible.
    405 Method Not Allowed
    A request was made of a resource using a request method not supported by that resource; for example, using GET on a form which requires data to be presented via POST, or using PUT on a read-only resource.
    406 Not Acceptable
    The requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request.
    407 Proxy Authentication Required
    The client must first authenticate itself with the proxy.
    408 Request Timeout
    The server timed out waiting for the request. According to W3 HTTP specifications: “The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time.”
    409 Conflict
    Indicates that the request could not be processed because of conflict in the request, such as an edit conflict.
    410 Gone
    Indicates that the resource requested is no longer available and will not be available again. This should be used when a resource has been intentionally removed and the resource should be purged. Upon receiving a 410 status code, the client should not request the resource again in the future. Clients such as search engines should remove the resource from their indices. Most use cases do not require clients and search engines to purge the resource, and a “404 Not Found” may be used instead.
    411 Length Required
    The request did not specify the length of its content, which is required by the requested resource.
    412 Precondition Failed
    The server does not meet one of the preconditions that the requester put on the request.
    413 Request Entity Too Large
    The request is larger than the server is willing or able to process.
    414 Request-URI Too Long
    The URI provided was too long for the server to process.
    415 Unsupported Media Type
    The request entity has a media type which the server or resource does not support. For example, the client uploads an image as image/svg+xml, but the server requires that images use a different format.
    416 Requested Range Not Satisfiable
    The client has asked for a portion of the file, but the server cannot supply that portion. For example, if the client asked for a part of the file that lies beyond the end of the file.
    417 Expectation Failed
    The server cannot meet the requirements of the Expect request-header field.[2]
    418 I’m a teapot (RFC 2324)
    This code was defined in 1998 as one of the traditional IETF April Fools’ jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers.
    420 Enhance Your Calm (Twitter)
    Not part of the HTTP standard, but returned by the Twitter Search and Trends API when the client is being rate limited. Other services may wish to implement the 429 Too Many Requests response code instead.
    422 Unprocessable Entity (WebDAV; RFC 4918)
    The request was well-formed but was unable to be followed due to semantic errors.
    423 Locked (WebDAV; RFC 4918)
    The resource that is being accessed is locked.
    424 Failed Dependency (WebDAV; RFC 4918)
    The request failed due to failure of a previous request (e.g. a PROPPATCH).
    424 Method Failure (WebDAV)
    Indicates the method was not executed on a particular resource within its scope because some part of the method’s execution failed causing the entire method to be aborted.
    425 Unordered Collection (Internet draft)
    Defined in drafts of “WebDAV Advanced Collections Protocol”, but not present in “Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol”.
    426 Upgrade Required (RFC 2817)
    The client should switch to a different protocol such as TLS/1.0.
    428 Precondition Required (RFC 6585)
    The origin server requires the request to be conditional. Intended to prevent “the ‘lost update’ problem, where a client GETs a resource’s state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict.”
    429 Too Many Requests (RFC 6585)
    The user has sent too many requests in a given amount of time. Intended for use with rate limiting schemes.
    431 Request Header Fields Too Large (RFC 6585)
    The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.
    444 No Response (Nginx)
    Used in Nginx logs to indicate that the server has returned no information to the client and closed the connection (useful as a deterrent for malware).
    449 Retry With (Microsoft)
    A Microsoft extension. The request should be retried after performing the appropriate action.
    Often search-engines or custom applications will ignore required parameters. Where no default action is appropriate, the Aviongoo website sends a “HTTP/1.1 449 Retry with valid parameters: param1, param2, . . .” response. The applications may choose to learn, or not.
    450 Blocked by Windows Parental Controls (Microsoft)
    A Microsoft extension. This error is given when Windows Parental Controls are turned on and are blocking access to the given webpage.
    451 Unavailable For Legal Reasons (Internet draft)
    Defined in the internet draft “A New HTTP Status Code for Legally-restricted Resources”. Intended to be used when resource access is denied for legal reasons, e.g.censorship or government-mandated blocked access. A reference to the 1953 dystopian novel Fahrenheit 451, where books are outlawed.
    451 Redirect (Microsoft)
    Used in Exchange ActiveSync if there either is a more efficient server to use or the server can’t access the users’ mailbox.
    The client is supposed to re-run the HTTP Autodiscovery protocol to find a better suited server.
    494 Request Header Too Large (Nginx)
    Nginx internal code similar to 431 but it was introduced earlier.
    495 Cert Error (Nginx)
    Nginx internal code used when SSL client certificate error occurred to distinguish it from 4XX in a log and an error page redirection.
    496 No Cert (Nginx)
    Nginx internal code used when client didn’t provide certificate to distinguish it from 4XX in a log and an error page redirection.
    497 HTTP to HTTPS (Nginx)
    Nginx internal code used for the plain HTTP requests that are sent to HTTPS port to distinguish it from 4XX in a log and an error page redirection.
    499 Client Closed Request (Nginx)
    Used in Nginx logs to indicate when the connection has been closed by client while the server is still processing its request, making server unable to send a status code back.

    Kode Server Error 5xx

    The server failed to fulfill an apparently valid request.

    Response status codes beginning with the digit “5” indicate cases in which the server is aware that it has encountered an error or is otherwise incapable of performing the request. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and indicate whether it is a temporary or permanent condition. Likewise, user agents should display any included entity to the user. These response codes are applicable to any request method.

    500 Internal Server Error
    A generic error message, given when no more specific message is suitable.
    501 Not Implemented
    The server either does not recognize the request method, or it lacks the ability to fulfill the request.
    502 Bad Gateway
    The server was acting as a gateway or proxy and received an invalid response from the upstream server.
    503 Service Unavailable
    The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.
    504 Gateway Timeout
    The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
    505 HTTP Version Not Supported
    The server does not support the HTTP protocol version used in the request.
    506 Variant Also Negotiates (RFC 2295)
    Transparent content negotiation for the request results in a circular reference.
    507 Insufficient Storage (WebDAV; RFC 4918)
    The server is unable to store the representation needed to complete the request.
    508 Loop Detected (WebDAV; RFC 5842)
    The server detected an infinite loop while processing the request (sent in lieu of 208).
    509 Bandwidth Limit Exceeded (Apache bw/limited extension)
    This status code, while used by many servers, is not specified in any RFCs.
    510 Not Extended (RFC 2774)
    Further extensions to the request are required for the server to fulfill it.
    511 Network Authentication Required (RFC 6585)
    The client needs to authenticate to gain network access. Intended for use by intercepting proxies used to control access to the network (e.g. “captive portals” used to require agreement to Terms of Service before granting full Internet access via a Wi-Fi hotspot).
    531 Access Denied (RFC 2229)
    The client’s authentication attempt was not successful.
    598 Network read timeout error (Unknown)
    This status code is not specified in any RFCs, but is used by Microsoft Corp. HTTP proxies to signal a network read timeout behind the proxy to a client in front of the proxy.
    599 Network connect timeout error (Unknown)
    This status code is not specified in any RFCs, but is used by Microsoft Corp. HTTP proxies to signal a network connect timeout behind the proxy to a client in front of the proxy.

     

     

    GmiB26.Net – Your Computer and Network Solution

    GmiB26.Net berlokasi di Perumahan Griya Mangli Indah B.26 kaliwates, Jember – JATIM. Bergerak dibidang Komputer dan Jaringan, Internet Unlimited via HotSpotLayanan Hosting dan Pendaftaran/Registrasi Domain Murah, Penjualan Pulsa All Operator dan Pembayaran Tagihan Online (PPOB)

    Post Tagged with , ,
Tell Your Friends About This Page!
upon digg

Leave a Reply

Your email address will not be published. Required fields are marked *

Your ip address : 54.87.18.165
Current Time : 20 March 2019 20:20:23 GMT+7