Knowledge base
1000 FAQs, 500 tutorials and instructional videos. Here, there are only solutions!
Understanding HTTP Errors
This guide helps you understand the different HTTP status codes.
1xx - Informational
Error 100: OK to continue
The server has received the request headers and the client can continue sending the request body.
Error 101: The server has switched protocols
The server accepts changing the communication protocol as requested by the client.
2xx - Success
Error 200: Request successful
The request was 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 processing is not yet complete.
Error 203: Request completed incompletely
The server has successfully processed the request, but the information returned comes from a third-party source.
Error 204: No information to return
The request was processed successfully, but there is no content to return.
Error 205: Request completed but form is empty
The server processed the request successfully and asks the client to reset the document that submitted the request.
Error 206: Incomplete GET request
The server only returns a portion 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 multiple 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 a different URL.
Error 303: Redirection with new access method
The response to the request can be found at a different 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: Redirect to a proxy specified by the header
The requested resource must be accessed through a specified proxy.
Error 307: Temporary Redirect
The requested resource is temporarily located under a different 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 requires payment
This code is reserved for future use regarding online payments. Services outside of Infomaniak use it in some cases to indicate a payment problem, but these uses are specific to these platforms – not a global standard.
Error 403: Access to the server is not authorized
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 allowed
The method specified in the request is not allowed for the target resource.
Error 406: Request not accepted by the server
The requested resource is unable to generate content acceptable according to the Accept headers sent in the request.
Error 407: Proxy authentication required
Access to the resource requires authentication through a proxy.
Error 408: Request timeout
The server did not receive the complete request within the allotted time.
Error 409: The user must resubmit with more information
The request could not 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 has been permanently removed.
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 failed.
Error 413: The request entity was too large
The server refuses to process the request because the size of the entity is too large.
Error 414: Request-URI 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 prevented it from fulfilling the request.
Error 501: Request made to the server is not supported
The server does not support the functionality required to process the request.
Error 502: Bad gateway
The server, acting as a gateway or proxy, received an invalid response from the upstream server.
Error 503: Service unavailable
The server is currently unavailable (overload or 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.
Link to this FAQ: https://faq.infomaniak.com/257
Has this FAQ been helpful?