HTTP Status Code:A Comprehensive Reviews 2025
100 Continue - ansThis means that the server has received the request headers, and that the client should
proceed to send the request body.
101 Switching Protocols - ansThis means the requester has asked the server to switch protocols and the server
is acknowledging that it will do so.
1xx Informational - ansRequest received, continuing process.
This class of status code indicates a provisional response, consisting only of the Status-Line and optional
headers, and is terminated by an empty line. Since HTTP/1.0 did not define any 1xx status codes, servers must
not send a 1xx response to an HTTP/1.0 client except under experimental conditions.
200 OK - ansStandard 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 - ansThe request has been fulfilled and resulted in a new resource being created.
202 Accepted - ansThe 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 (since HTTP/1.1) - ansThe server successfully processed the request, but is
returning information that may be from another source.
204 No Content - ansThe server successfully processed the request, but is not returning any content.
205 Reset Content - ansThe 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 - ansThe server is delivering only part of the resource due to a range header sent by the
client. The range header is used by tools like wget to enable resuming of interrupted downloads, or split a
download into multiple simultaneous streams.
2xx Success - ansThis class of status codes indicates the action requested by the client was received,
understood, accepted and processed successfully.
300 Multiple Choices - ansIndicates 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 - ansThis and all future requests should be directed to the given URI.
302 Found - ansThis is an example of industry practice contradicting the standard. The 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 302 with the functionality of a 303 See Other. Therefore,
HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviours. However, some Web
applications and frameworks use the 302 status code as if it were the 303.
303 See Other - ansThe response to the request can be found under another URI using a GET method. When
received in response to a POST (or PUT/DELETE), 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 - ansIndicates 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. Using
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 sent again using
more bandwidth of the server and client.
305 Use Proxy (since HTTP/1.1) - ansMany HTTP clients (such as Mozilla and Internet Explorer) do not correctly
handle responses with this status code, primarily for security reasons.
100 Continue - ansThis means that the server has received the request headers, and that the client should
proceed to send the request body.
101 Switching Protocols - ansThis means the requester has asked the server to switch protocols and the server
is acknowledging that it will do so.
1xx Informational - ansRequest received, continuing process.
This class of status code indicates a provisional response, consisting only of the Status-Line and optional
headers, and is terminated by an empty line. Since HTTP/1.0 did not define any 1xx status codes, servers must
not send a 1xx response to an HTTP/1.0 client except under experimental conditions.
200 OK - ansStandard 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 - ansThe request has been fulfilled and resulted in a new resource being created.
202 Accepted - ansThe 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 (since HTTP/1.1) - ansThe server successfully processed the request, but is
returning information that may be from another source.
204 No Content - ansThe server successfully processed the request, but is not returning any content.
205 Reset Content - ansThe 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 - ansThe server is delivering only part of the resource due to a range header sent by the
client. The range header is used by tools like wget to enable resuming of interrupted downloads, or split a
download into multiple simultaneous streams.
2xx Success - ansThis class of status codes indicates the action requested by the client was received,
understood, accepted and processed successfully.
300 Multiple Choices - ansIndicates 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 - ansThis and all future requests should be directed to the given URI.
302 Found - ansThis is an example of industry practice contradicting the standard. The 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 302 with the functionality of a 303 See Other. Therefore,
HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviours. However, some Web
applications and frameworks use the 302 status code as if it were the 303.
303 See Other - ansThe response to the request can be found under another URI using a GET method. When
received in response to a POST (or PUT/DELETE), 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 - ansIndicates 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. Using
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 sent again using
more bandwidth of the server and client.
305 Use Proxy (since HTTP/1.1) - ansMany HTTP clients (such as Mozilla and Internet Explorer) do not correctly
handle responses with this status code, primarily for security reasons.
