By browsing the Internet, we sometimes see 404 Page not found or 503 Service unavailable error. Also read more various HTTP success or error codes. But many people do not know about those codes containing different numbers, so today I will try to give a little bit about these codes on these tunes.
Codes starting with 1 mean that the request has been received on the server, and the request is being processed.
101 Switching Protocols
By this code, the requesting server is requesting the server to switch protocols and the server responded.
As such a WebDAV request may contain many sub-requests, it may take a long time to perform such a request. Such code implies that the request was received by the server and the server is processing the request but no response is available till now. As a result, the client understands that the work is going on and its request is not lost.
2xx Success
This status status code indicates that the request requested by the client is accepted, it is understood, approved and processed successfully.
202 Accepted
204 No Content
206 Partial Content
3xx Redirection
If and only if the GET or HEAD method is used for the second request, then that action will be edited with user agent without any interaction with the user. The user agent will not be able to redirect any request more than five minutes, because it can be understood that such redirection is creating an indefinite loop.
301 Moved Permanently
This code and all future requests will be directed to the given URL.
_B296487
302 Found
This is the most popular redirect code, but it is an industrial practice that is opposed to the standard principles. According to HTTP / 1.0, a client can redirect only temporary, but the popular browser has implemented 302 code like 303 see other code. That's why HTTP / 1.1 has added the status code 303 and 307, so that these two different behaviors are different. However, most web applications and frameworks still use the 302 status code in such a way that it is 303.
303 See Other (since HTTP / 1.1)
This code means that the response to the request will be available from another URL with the GET method. When such code is available as a response to PUT, it should be understood that the server has received the data and the redirect should be issued with another GET message.
304 Not Modified
This code means that the resource has not been modified after the latest request.
305 Use Proxy (since HTTP / 1.1)
Due to primary security, many HTTP clients like Mozilla and Internet Explorer do not respond properly with the status codes.
306 Switch Proxy
Is not used anymore.
307 Temporary Redirect (since HTTP / 1.1)
For this code, you will need to re-request via any other URI. However, the future URIs can be used in future requests. To compare with 303, the request method can not be changed during the re-issue of the request. For example: A POST request must be used again while issuing another POST request.
4xx Client Error
This class status code is used when the client makes a mistake. Only with HEAD request, the server adds an NTT with the explanation of the error, and also informs that this situation is not permanent or temporary. This status code applies to any request method. In this case, the agent's agent displays all the associated NTTs. Below are the most commonly used error codes:
400 Bad Request
This code indicates that there is a mistake in stepping in the request.
401 Unauthorized
It is similar to the 403 Forbidden code but only authentication is possible.
402 Payment Required
This code is stored for future use. Actually, the real purpose is that the code is usually meant to be used as a part of the scheme of digital cass or microphimation, since this code has never been used.
jamalgota_1221321151_1-3
403 Forbidden
The request was a legal request, but the server refuses to respond to the request.
error403
404 Not Found
The requested resource is currently not available, but it can be found in the future. Further approval of the client is allowed.
normal_funny_Error_404
405 Method Not Allowed
This code is requested by means of a resource that does not support those resources. For example: using the GET method where POST is required, this status code will be displayed.
406 Not Acceptable
The requested resource is only capable of producing content that is not acceptable according to Accept Headers sent with the request.
408 Request Timeout
The server's time is out for the request to wait for the request.
409 Conflict
This code indicates that the request is not being executed because the request has conflict. Such as: Edit-conflict
410 Gone
This code means that the requested resource is no longer available and there is no possibility of getting it in the future.
05_23_1 --- Graveyard_web
411 Length Required
This code indicates that the content is not provided with the length of the content, which is applicable to the requested resource.
412 Precondition Failed
The request does not comply with a prerequisite in the Requestor's request.
413 Request Entity Too Large
This means that the requesting server is more than the authorized or approved.
414 Request-URI Too Long </ span>
This code means that the provided URI is big enough for the server to process.
415 Unsupported Media Type
This means that no media files that server or resource support have been requested.
416 Requested Range Not Satisfiable
The code indicates that the client requested only one part of a file, but the server could not supply that note.
417 Expectation Failed
The applicability of the Expect request-header field by the code does not match the capability of the server.
418 I'm a teapot
The HTCPCP server implies a teapot. According to the RFC 2324, Hyper Text Coffee Pot Control Protocol, the code is interpreted as a traditional IETF April Fools' jokes.
422 Unprocessable Entity (WebDAV) (RFC 4918)
The code was correct, but it is not possible to follow it because of its meaning.
423 Locked (WebDAV) (RFC 4918)
The code indicates that the resource requested is locked.
424 Failed Dependency (WebDAV) (RFC 4918)
The request also failed because the previous request failed.
425 Unordered Collection (RFC 3648)
The code can be found in the "WebDAV Advanced Collections Protocol" but is not "Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol".
426 Upgrade Required (RFC 2817)
This code means the client needs to switch to other protocols such as TLS / 1.0.
449 Retry With
This refers to a Microsoft extension and means that it will be re-requested after performing the correct operation.
450 Blocked by Windows Parental Controls
It also refers to a Microsoft extension. When the Windows parental control is turned on, the code is displayed and the access to the requested webpage is turned off.
5xx Server Error
These class codes are displayed only when the server apparently fails to fill a valid request.
Having "5" at the beginning of Response Status Code means there is an error in the server or it is not capable of performing a request. Apart from the HEAD file, on the other hand, the server responds with an explanation of the error and adds an NTT and gives an idea of the lasting error. User agent will display the specified NTT user.
The response code below applies to any request method:
500 Internal Server Error
This code displays the status code when the server does not find any reason for the problem.
internalservererror
501 Not Implemented
This means that the server does not understand the request request or it is unable to fulfill the request.
502 Bad Gateway
From this code it is understood that the server was acting as a gateway or proxy and received an in-valid response from the down-stream server.
503 Service Unavailable
This means the server is currently closed. Generally, this code is used to mean temporary condition.
504 Gateway Timeout
The code explains from this code: The server was acting as a gateway or proxy and it failed to get a request from time to down-stream server.
505 HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request.
506 Variant Negotiates (RFC 2295)
This code means that a cyclical reference has been created as a result of transparent content-negotiation for the request.
507 Insufficient Storage (WebDAV) (RFC 4918)
There is not enough space to complete this request.
p1
509 Bandwidth Limit Exceeded (Apache bw / limited extension)
This status code refers to the amount of bandwidth required to complete the request, not to the RFCs.
510 Not Extended (RFC 2774) </ span>
This means that the server requires a more extended extension to fulfill the request.
1xx Informationall
Codes starting with 1 mean that the request has been received on the server, and the request is being processed.
(Just like the status line and the optional headers, this type of status code indicates the response to different conditions, since 1xx status code in HTTP / 1.0 is not used, so the server must send 1xx Response to an HTTP / 1.0 client without any experimental conditions. No.)
100 continue
This implies that the requested recruited headers are received on the server, and the client can send the requested request. If a request failed on the server due to an incorrect header, it would be futile to send a large requested body to the server. To know whether the request will be accepted based on the header only, a client must send the Expect: 100-release code as the initial request of the headers and before starting the job, it must be checked that the 100-continue status Code received by server. (If the server responds as 417 Expectation Failed code should not be continued.)101 Switching Protocols
By this code, the requesting server is requesting the server to switch protocols and the server responded.
102 Processing (WebDAV) (RFC 2518)
As such a WebDAV request may contain many sub-requests, it may take a long time to perform such a request. Such code implies that the request was received by the server and the server is processing the request but no response is available till now. As a result, the client understands that the work is going on and its request is not lost.
2xx Success
This status status code indicates that the request requested by the client is accepted, it is understood, approved and processed successfully.
200 OK
This is an ideal response to a successful HTTP request. Actual response usually depends on the request method. In relation to a GET request, the response "has an NTT request request with the requested resource. In relation to the POST request, the explanation or results of the requested work is included with the reply.
201 Created
This code implies that the request has been received, resulting in a new resource being created.
202 Accepted
This is the request, the request was received for processing, but the processing was not edited.
203 Non-Authoritative Information (since HTTP / 1.1)
The server has successfully executed the request, but the information it receives from is likely coming from another source.
204 No Content
This code means that the server successfully processed the request, but there is no content.
205 Reset Content
The server successfully requested the request, but no content is coming. Responding to a slightly different code than 204 codes, the respondent asks the applicant to reset his document view.
206 Partial Content
This code means sending a portion of the server resource to the client's sent range header. This code is used by wget tools for download, resume, interrupted downloads and a download simultaneously via multiple streams.
207 MultiDA Status (RFC 2518)
This code means that the body of the message is an XML message, which holds different response codes for different sub-requests.
3xx Redirection
In relation to this class code, it means that the client must be redirected to edit the request.
If and only if the GET or HEAD method is used for the second request, then that action will be edited with user agent without any interaction with the user. The user agent will not be able to redirect any request more than five minutes, because it can be understood that such redirection is creating an indefinite loop.
301 Moved Permanently
This code and all future requests will be directed to the given URL.
_B296487
302 Found
This is the most popular redirect code, but it is an industrial practice that is opposed to the standard principles. According to HTTP / 1.0, a client can redirect only temporary, but the popular browser has implemented 302 code like 303 see other code. That's why HTTP / 1.1 has added the status code 303 and 307, so that these two different behaviors are different. However, most web applications and frameworks still use the 302 status code in such a way that it is 303.
303 See Other (since HTTP / 1.1)
This code means that the response to the request will be available from another URL with the GET method. When such code is available as a response to PUT, it should be understood that the server has received the data and the redirect should be issued with another GET message.
304 Not Modified
This code means that the resource has not been modified after the latest request.
305 Use Proxy (since HTTP / 1.1)
Due to primary security, many HTTP clients like Mozilla and Internet Explorer do not respond properly with the status codes.
306 Switch Proxy
Is not used anymore.
307 Temporary Redirect (since HTTP / 1.1)
For this code, you will need to re-request via any other URI. However, the future URIs can be used in future requests. To compare with 303, the request method can not be changed during the re-issue of the request. For example: A POST request must be used again while issuing another POST request.
4xx Client Error
This class status code is used when the client makes a mistake. Only with HEAD request, the server adds an NTT with the explanation of the error, and also informs that this situation is not permanent or temporary. This status code applies to any request method. In this case, the agent's agent displays all the associated NTTs. Below are the most commonly used error codes:
301 Moved Permanently
This code and all future requests will be directed to the given URL.
_B296487
302 Found
This is the most popular redirect code, but it is an industrial practice that is opposed to the standard principles. According to HTTP / 1.0, a client can redirect only temporary, but the popular browser has implemented 302 code like 303 see other code. That's why HTTP / 1.1 has added the status code 303 and 307, so that these two different behaviors are different. However, most web applications and frameworks still use the 302 status code in such a way that it is 303.
303 See Other (since HTTP / 1.1)
This code means that the response to the request will be available from another URL with the GET method. When such code is available as a response to PUT, it should be understood that the server has received the data and the redirect should be issued with another GET message.
304 Not Modified
This code means that the resource has not been modified after the latest request.
305 Use Proxy (since HTTP / 1.1)
Due to primary security, many HTTP clients like Mozilla and Internet Explorer do not respond properly with the status codes.
306 Switch Proxy
Is not used anymore.
307 Temporary Redirect (since HTTP / 1.1)
For this code, you will need to re-request via any other URI. However, the future URIs can be used in future requests. To compare with 303, the request method can not be changed during the re-issue of the request. For example: A POST request must be used again while issuing another POST request.
4xx Client Error
This class status code is used when the client makes a mistake. Only with HEAD request, the server adds an NTT with the explanation of the error, and also informs that this situation is not permanent or temporary. This status code applies to any request method. In this case, the agent's agent displays all the associated NTTs. Below are the most commonly used error codes:
301 Moved Permanently
This code and all future requests will be directed to the given URL.
_B296487
302 Found
This is the most popular redirect code, but it is an industrial practice that is opposed to the standard principles. According to HTTP / 1.0, a client can redirect only temporary, but the popular browser has implemented 302 code like 303 see other code. That's why HTTP / 1.1 has added the status code 303 and 307, so that these two different behaviors are different. However, most web applications and frameworks still use the 302 status code in such a way that it is 303.
303 See Other (since HTTP / 1.1)
This code means that the response to the request will be available from another URL with the GET method. When such code is available as a response to PUT, it should be understood that the server has received the data and the redirect should be issued with another GET message.
304 Not Modified
This code means that the resource has not been modified after the latest request.
305 Use Proxy (since HTTP / 1.1)
Due to primary security, many HTTP clients like Mozilla and Internet Explorer do not respond properly with the status codes.
306 Switch Proxy
Is not used anymore.
307 Temporary Redirect (since HTTP / 1.1)
For this code, you will need to re-request via any other URI. However, the future URIs can be used in future requests. To compare with 303, the request method can not be changed during the re-issue of the request. For example: A POST request must be used again while issuing another POST request.
4xx Client Error
This class status code is used when the client makes a mistake. Only with HEAD request, the server adds an NTT with the explanation of the error, and also informs that this situation is not permanent or temporary. This status code applies to any request method. In this case, the agent's agent displays all the associated NTTs. Below are the most commonly used error codes:
This code indicates that there is a mistake in stepping in the request.
401 Unauthorized
It is similar to the 403 Forbidden code but only authentication is possible.
402 Payment Required
This code is stored for future use. Actually, the real purpose is that the code is usually meant to be used as a part of the scheme of digital cass or microphimation, since this code has never been used.
jamalgota_1221321151_1-3
403 Forbidden
The request was a legal request, but the server refuses to respond to the request.
error403
404 Not Found
The requested resource is currently not available, but it can be found in the future. Further approval of the client is allowed.
normal_funny_Error_404
405 Method Not Allowed
This code is requested by means of a resource that does not support those resources. For example: using the GET method where POST is required, this status code will be displayed.
406 Not Acceptable
The requested resource is only capable of producing content that is not acceptable according to Accept Headers sent with the request.
408 Request Timeout
The server's time is out for the request to wait for the request.
409 Conflict
This code indicates that the request is not being executed because the request has conflict. Such as: Edit-conflict
410 Gone
This code means that the requested resource is no longer available and there is no possibility of getting it in the future.
05_23_1 --- Graveyard_web
411 Length Required
This code indicates that the content is not provided with the length of the content, which is applicable to the requested resource.
412 Precondition Failed
The request does not comply with a prerequisite in the Requestor's request.
413 Request Entity Too Large
This means that the requesting server is more than the authorized or approved.
414 Request-URI Too Long </ span>
This code means that the provided URI is big enough for the server to process.
415 Unsupported Media Type
This means that no media files that server or resource support have been requested.
416 Requested Range Not Satisfiable
The code indicates that the client requested only one part of a file, but the server could not supply that note.
417 Expectation Failed
The applicability of the Expect request-header field by the code does not match the capability of the server.
418 I'm a teapot
The HTCPCP server implies a teapot. According to the RFC 2324, Hyper Text Coffee Pot Control Protocol, the code is interpreted as a traditional IETF April Fools' jokes.
422 Unprocessable Entity (WebDAV) (RFC 4918)
The code was correct, but it is not possible to follow it because of its meaning.
423 Locked (WebDAV) (RFC 4918)
The code indicates that the resource requested is locked.
424 Failed Dependency (WebDAV) (RFC 4918)
The request also failed because the previous request failed.
425 Unordered Collection (RFC 3648)
The code can be found in the "WebDAV Advanced Collections Protocol" but is not "Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol".
426 Upgrade Required (RFC 2817)
This code means the client needs to switch to other protocols such as TLS / 1.0.
449 Retry With
This refers to a Microsoft extension and means that it will be re-requested after performing the correct operation.
450 Blocked by Windows Parental Controls
It also refers to a Microsoft extension. When the Windows parental control is turned on, the code is displayed and the access to the requested webpage is turned off.
5xx Server Error
These class codes are displayed only when the server apparently fails to fill a valid request.
Having "5" at the beginning of Response Status Code means there is an error in the server or it is not capable of performing a request. Apart from the HEAD file, on the other hand, the server responds with an explanation of the error and adds an NTT and gives an idea of the lasting error. User agent will display the specified NTT user.
The response code below applies to any request method:
500 Internal Server Error
This code displays the status code when the server does not find any reason for the problem.
internalservererror
501 Not Implemented
This means that the server does not understand the request request or it is unable to fulfill the request.
502 Bad Gateway
From this code it is understood that the server was acting as a gateway or proxy and received an in-valid response from the down-stream server.
503 Service Unavailable
This means the server is currently closed. Generally, this code is used to mean temporary condition.
504 Gateway Timeout
The code explains from this code: The server was acting as a gateway or proxy and it failed to get a request from time to down-stream server.
505 HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request.
506 Variant Negotiates (RFC 2295)
This code means that a cyclical reference has been created as a result of transparent content-negotiation for the request.
507 Insufficient Storage (WebDAV) (RFC 4918)
There is not enough space to complete this request.
p1
509 Bandwidth Limit Exceeded (Apache bw / limited extension)
This status code refers to the amount of bandwidth required to complete the request, not to the RFCs.
510 Not Extended (RFC 2774) </ span>
This means that the server requires a more extended extension to fulfill the request.