This guide helps you understand the different HTTP status codes.

1xx - Information

error 100: Continue
The server has received the request headers and the client may continue to send the request body.

error 101: Switching Protocols
The server agrees to switch the communication protocol according to the client's request.

2xx - Success

error 200: Request executed successfully
The request has been successfully processed by the server.

error 201: Document created (reason: new URI)
The request was successful and resulted in the creation of a new resource.

error 202: Request completed asynchronously (TBS)
The request has been accepted but the processing is not yet complete.

error 203: Request completed incompletely
The server successfully processed the request, but the returned information comes from a third-party source.

error 204: No information to return
The request was successfully processed, but there is no content to return.

error 205: Request completed but form empty
The server successfully processed the request and asks the client to reset the document that submitted the request.

error 206: Incomplete GET request
The server returns only part of the data, as requested by the client with the Range header.

3xx - Redirections

error 300: The server cannot determine the return code
The request has several possible responses, and the server cannot automatically choose one of them.

error 301: Document permanently moved
The requested resource has been permanently moved to a new URL.

error 302: Document temporarily moved
The requested resource is temporarily located at another URL.

error 303: Redirection with new access method
The response to the request can be found under another URL using a GET method.

error 304: The 'If-Modified-Since' field was not modified
The resource has not been modified since the last request. No new data will be returned.

error 305: Redirection to a proxy specified by the header
The requested resource must be accessed through a specified proxy.

error 307: Temporary redirection
The requested resource is temporarily located at another URL, but the client must use the same method to make the next request.

4xx - Client errors

error 400: Syntax error in the document address
The request is incorrect or malformed.

error 401: No authorization to access the document
Access to the resource requires authentication.

error 402: Access to the document subject to payment
This code is reserved for future use regarding online payments. Some services outside of Infomaniak use it in certain cases to indicate a payment issue, but these uses are specific to these platforms — not a global standard.

error 403: No authorization to access the server
The server understands the request but refuses to authorize it.

error 404: The requested page does not exist
The server cannot find the requested resource.

error 405: Form request method not authorized
The method specified in the request is not authorized for the target resource.

error 406: Request not accepted by the server
The requested resource is not capable of generating acceptable content according to the Accept headers sent in the request.

error 407: Proxy authorization required
Access to the resource requires authentication by a proxy.

error 408: Access time to the requested page expired
The server did not receive the complete request within the allotted time.

error 409: The user must resubmit with more information
The request cannot be processed due to a conflict with the current state of the resource.

error 410: This resource is no longer available
The requested resource is no longer available and this is permanent.

error 411: The server refused the request because it has no length
The server refuses to process the request without a valid Content-Length header.

error 412: The precondition given in the request failed
One of the conditions specified in the request headers has failed.

error 413: The request entity was too large
The server refuses to process the request because the entity size is too large.

error 414: The request URI was too long
The server refuses to process the request because the URI is too long.

error 415: Unsupported media type
The server refuses to process the request because the format of the request entity is not supported.

5xx - Server errors

error 500: Internal server error
The server encountered an unexpected condition that prevents it from processing the request.

error 501: Request made to the server not supported
The server does not support the functionality required to process the request.

error 502: Bad gateway access
The server, acting as a gateway or proxy, received an invalid response from the upstream server.

Error 503: Service unavailable
The server is not available at the moment (overloaded or undergoing maintenance).

Error 504: Gateway timeout
The server, acting as a gateway or proxy, did not receive a timely response from the upstream server.

Error 505: HTTP version not supported
The server does not support the HTTP protocol version used in the request.