100100 Continue
The server has received the request headers and the client should proceed to send the request body.
Comprehensive reference for developer error codes — search, understand, and fix errors across 15 programming languages and platforms.
1360 error codes found
100The server has received the request headers and the client should proceed to send the request body.
101The server is switching protocols as requested by the client via an Upgrade header.
102The server has received and is processing the request, but no response is available yet (WebDAV).
103The server sends preliminary response headers to allow the client to start preloading resources before the final response.
200The request has succeeded. The meaning of the success depends on the HTTP method used.
201The request has been fulfilled and a new resource has been created as a result.
202The request has been accepted for processing, but the processing has not been completed yet.
203The response has been modified by a transforming proxy and differs from what the origin server sent.
204The server successfully processed the request but is not returning any content in the response body.
205The server tells the client to reset the document view, such as clearing a form after submission.
206The server is delivering only part of the resource due to a Range header sent by the client.
207The response provides status for multiple independent operations in a single response (WebDAV).
208The members of a DAV binding have already been enumerated in a previous part of the response, and are not included again.
226The server has fulfilled a GET request and the response is a representation of the result of one or more instance-manipulations applied to the current instance.
300The request has more than one possible response and the user or user agent should choose one of them.
301The requested resource has been permanently moved to a new URL, and future requests should use the new URL.
302The requested resource temporarily resides at a different URL. Future requests should continue to use the original URL.
303The response to the request can be found at a different URL using a GET method.
304The resource has not been modified since the last request, so the client can use its cached copy.
305The requested resource must be accessed through the proxy specified in the Location header. This status code is deprecated.
307The request should be repeated with the same method at the URL in the Location header. Unlike 302, the request method must not change.
308The resource has permanently moved to a new URL, and the request method must not change when following the redirect.
400The server cannot process the request due to a client error, such as malformed syntax, invalid parameters, or corrupt data.
401The request requires user authentication. The client must provide valid credentials to access the resource.