Daftar Nomor-Nomor Error yang Terjadi pada Server

Pernahkah anda mengalami salah satu error berikut ini serperti 404 page not found, 500 Internal server error, 502 bad gateway, 403 Forbidden dan sebagainya.

Itu berarti ada masalah error dengan server yang kita tuju, atau bisa berarti ada kesalahan dengan link yang kita akses.

Seringkali kita mendapatkan respon error dari suatu website, salah satunya yang paling sering 404 page not found, yang berarti link yang kita akses tidak ada. Kesalahan bisa terjadi karena human error dari kesalahan pengetikan link, atau memang website tersebut halamannya sudah terhapus, apabila kita menggunakan link yang disediakan dari website tersebut. atau bisa kita sebut broken link.

Maka itu kita jangan kaget, mari kita kenali nomor-nomor error yang terjadi dari respon server yang kita request. Berikut daftar error respon server yang biasa terjadi :

100 Continue
    ErrorDocument Continue | Sample 100 Continue
    This means that the server has received the request headers, and that the client should proceed to send the request body (in case of a request which needs to be sent; for example, a POST request). If the request body is large, sending it to a server when a request has already been rejected based upon inappropriate headers is inefficient. To have a server check if the request could be accepted based on the requests headers alone, a client must send Expect: 100-continue as a header in its initial request (see RFC 2616 14.20 Expect header) and check if a 100 Continue status code is received in response before continuing (or receive 417 Expectation Failed and not continue).

101 Switching Protocols
    ErrorDocument Switching Protocols | Sample 101 Switching Protocols
    This means the requester has asked the server to switch protocols and the server is acknowledging that it will do so.

102 Processing
    ErrorDocument Processing | Sample 102 Processing
    (WebDAV) - (RFC 2518 )

200 OK
    ErrorDocument OK | Sample 200 OK
    Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request the response will contain an entity describing or containing the result of the action.

201 Created
    ErrorDocument Created | Sample 201 Created
    The request has been fulfilled and resulted in a new resource being created.

202 Accepted
    ErrorDocument Accepted | Sample 202 Accepted
    The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place.

203 Non-Authoritative Information
    ErrorDocument Non-Authoritative Information | Sample 203 Non-Authoritative Information
    The server successfully processed the request, but is returning information that may be from another source.

204 No Content
    ErrorDocument No Content | Sample 204 No Content
    The server successfully processed the request, but is not returning any content.

205 Reset Content
    ErrorDocument Reset Content | Sample 205 Reset Content
    The server successfully processed the request, but is not returning any content. Unlike a 204 response, this response requires that the requester reset the document view.

206 Partial Content
    ErrorDocument Partial Content | Sample 206 Partial Content
    The server is delivering only part of the resource due to a range header sent by the client. This is used by tools like wget to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.

207 Multi-Status
    ErrorDocument Multi-Status | Sample 207 Multi-Status
    (WebDAV) - The message body that follows is an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.

226 IM Used
    ErrorDocument IM Used | Sample 226 IM Used
    The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance. The actual current instance might not be available except by combining this response with other previous or future responses, as appropriate for the specific instance-manipulation(s).

300 Multiple Choices
    ErrorDocument Multiple Choices | Sample 300 Multiple Choices
    Indicates multiple options for the resource that the client may follow. It, for instance, could be used to present different format options for video, list files with different extensions, or word sense disambiguation.

301 Moved Permanently
    ErrorDocument Moved Permanently | Sample 301 Moved Permanently
    This and all future requests should be directed to the given URI.

302 Found
    ErrorDocument Found | Sample 302 Found
    This is the most popular redirect code[citation needed], but also an example of industrial practice contradicting the standard. HTTP/1.0 specification (RFC 1945 ) required the client to perform a temporary redirect (the original describing phrase was "Moved Temporarily"), but popular browsers implemented it as a 303 See Other. Therefore, HTTP/1.1 added status codes 303 and 307 to disambiguate between the two behaviours. However, the majority of Web applications and frameworks still use the 302 status code as if it were the 303.

303 See Other
    ErrorDocument See Other | Sample 303 See Other
    The response to the request can be found under another URI using a GET method. When received in response to a PUT, it should be assumed that the server has received the data and the redirect should be issued with a separate GET message.

304 Not Modified
    ErrorDocument Not Modified | Sample 304 Not Modified
    Indicates the resource has not been modified since last requested. Typically, the HTTP client provides a header like the If-Modified-Since header to provide a time against which to compare. Utilizing this saves bandwidth and reprocessing on both the server and client, as only the header data must be sent and received in comparison to the entirety of the page being re-processed by the server, then resent using more bandwidth of the server and client.

305 Use Proxy
    ErrorDocument Use Proxy | Sample 305 Use Proxy
    Many HTTP clients (such as Mozilla[4] and Internet Explorer) do not correctly handle responses with this status code, primarily for security reasons.

306 Switch Proxy
    ErrorDocument Switch Proxy | Sample 306 Switch Proxy
    No longer used.

307 Temporary Redirect
    ErrorDocument Temporary Redirect | Sample 307 Temporary Redirect
    In this occasion, the request should be repeated with another URI, but future requests can still use the original URI. In contrast to 303, the request method should not be changed when reissuing the original request. For instance, a POST request must be repeated using another POST request.

400 Bad Request
    ErrorDocument Bad Request | Sample 400 Bad Request
    The request contains bad syntax or cannot be fulfilled.

401 Unauthorized
    ErrorDocument Unauthorized | Sample 401 Unauthorized
    Similar to 403 Forbidden, but specifically for use when authentication is possible but has failed or 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
    ErrorDocument Payment Required | Sample 402 Payment Required
    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 has never been used.

403 Forbidden
    ErrorDocument Forbidden | Sample 403 Forbidden
    The request was a legal request, but the server is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference.

404 Not Found
    ErrorDocument Not Found | Sample 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
    ErrorDocument Method Not Allowed | Sample 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
    ErrorDocument Not Acceptable | Sample 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
    ErrorDocument Proxy Authentication Required | Sample

407 Proxy Authentication Required
    Required

408 Request Timeout
    ErrorDocument Request Timeout | Sample 408 Request Timeout
    The server timed out waiting for the request.

409 Conflict
    ErrorDocument Conflict | Sample 409 Conflict
    Indicates that the request could not be processed because of conflict in the request, such as an edit conflict.

410 Gone
    ErrorDocument Gone | Sample 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; however, it is not necessary to return this code and a 404 Not Found can be issued instead. 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 indexes.

411 Length Required
    ErrorDocument Length Required | Sample 411 Length Required
    The request did not specify the length of its content, which is required by the requested resource.

412 Precondition Failed
    ErrorDocument Precondition Failed | Sample 412 Precondition Failed
    The server does not meet one of the preconditions that the requester put on the request.

413 Request Entity Too Large
    ErrorDocument Request Entity Too Large | Sample 413 Request Entity Too Large
    The request is larger than the server is willing or able to process.

414 Request-URI Too Long
    ErrorDocument Request-URI Too Long | Sample 414 Request-URI Too Long
    The URI provided was too long for the server to process.

415 Unsupported Media Type
    ErrorDocument Unsupported Media Type | Sample 415 Unsupported Media Type
    The request did not specify any media types that the server or resource supports. For example the client specified that an image resource should be served as image/svg xml, but the server cannot find a matching version of the image.

416 Requested Range Not Satisfiable
    ErrorDocument Requested Range Not Satisfiable | Sample 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
    ErrorDocument Expectation Failed | Sample 417 Expectation Failed
    The server cannot meet the requirements of the Expect request-header field.

418 I'm a teapot
    ErrorDocument I'm a teapot | Sample 418 I'm a teapot
    The HTCPCP server is a teapot. The responding entity MAY be short and stout. Defined by the April Fools specification RFC 2324. See Hyper Text Coffee Pot Control Protocol for more information.

422 Unprocessable Entity
    ErrorDocument Unprocessable Entity | Sample 422 Unprocessable Entity
    (WebDAV) (RFC 4918 ) - The request was well-formed but was unable to be followed due to semantic errors.

423 Locked
    ErrorDocument Locked | Sample 423 Locked
    (WebDAV) (RFC 4918 ) - The resource that is being accessed is locked

424 Failed Dependency
    ErrorDocument Failed Dependency | Sample 424 Failed Dependency
    (WebDAV) (RFC 4918 ) - The request failed due to failure of a previous request (e.g. a PROPPATCH).

425 Unordered Collection
    ErrorDocument Unordered Collection | Sample 425 Unordered Collection
    Defined in drafts of WebDav Advanced Collections, but not present in "Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol" (RFC 3648).

426 Upgrade Required
    ErrorDocument Upgrade Required | Sample 426 Upgrade Required
    (RFC 2817 ) - The client should switch to TLS/1.0.

449 Retry With
    ErrorDocument Retry With | Sample 449 Retry With
    A Microsoft extension. The request should be retried after doing the appropriate action.

500 Internal Server Error
    ErrorDocument Internal Server Error | Sample 500 Internal Server Error
    A generic error message, given when no more specific message is suitable.

501 Not Implemented
    ErrorDocument Not Implemented | Sample 501 Not Implemented
    The server either does not recognise the request method, or it lacks the ability to fulfil the request.

502 Bad Gateway
    ErrorDocument Bad Gateway | Sample 502 Bad Gateway
    The server was acting as a gateway or proxy and received an invalid response from the upstream server.

503 Service Unavailable
    ErrorDocument Service Unavailable | Sample 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
    ErrorDocument Gateway Timeout | Sample 504 Gateway Timeout
    The server was acting as a gateway or proxy and did not receive a timely request from the upstream server.

505 HTTP Version Not Supported
    ErrorDocument HTTP Version Not Supported | Sample

505 HTTP Version Not Supported
    The server does not support the HTTP protocol version used in the request.

506 Variant Also Negotiates
    ErrorDocument Variant Also Negotiates | Sample 506 Variant Also Negotiates
    (RFC 2295 ) - Transparent content negotiation for the request, results in a circular reference.

507 Insufficient Storage
    ErrorDocument Insufficient Storage | Sample 507 Insufficient Storage
    (WebDAV) (RFC 4918 )

509 Bandwidth Limit Exceeded
    ErrorDocument Bandwidth Limit Exceeded | Sample 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
    ErrorDocument Not Extended | Sample 510 Not Extended
    (RFC 2774 ) - Further extensions to the request are required for the server to fulfil it.