How can we help you?

Standart HTTP Errors list

Understanding HTTP Error Codes for eCommerce Data Migration

When performing an eCommerce data migration, understanding HTTP error codes can be crucial for troubleshooting potential issues. Here's a breakdown of common HTTP error codes you might encounter:

Redirection Errors (3xx) During Data Migration

Redirection errors indicate that the client needs to take additional action to complete the request. While less common in the core data migration process itself, they can occur when the source or target store has redirection rules in place that interfere with data access.

300 Multiple Choices - Indicates multiple options for the resource that the client may follow.

301 Moved Permanently - This and all future requests should be directed to the given URL. This is a permanent redirect.

302 Found - Requires the client to perform a temporary redirect (the original describing phrase was "Moved Temporarily"). This is a temporary redirect.

303 See Other - The response to the request can be found under another URL using a GET method.

304 Not Modified - Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-Match.

306 Switch Proxy - No longer used. Originally meant "Subsequent requests should use the specified proxy."

307 Temporary Redirect (since HTTP/1.1) - In this case, the request should be repeated with another URL; however, future requests should still use the original URL. This is a temporary redirect.

308 Permanent Redirect - The request, and all future requests should be repeated using another URL. This is a permanent redirect.

Client Errors (4xx) Impacting eCommerce Data Migration

Client errors indicate that the request contains bad syntax or cannot be fulfilled. These are often the most common errors encountered during data migration, indicating issues with access permissions, incorrect URLs, or missing data.

400 Bad Request - The request cannot be fulfilled due to bad syntax.

401 Unauthorized - Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.

402 Payment Required - Reserved for future use.

403 Forbidden - The request was a valid request, but the server is refusing to respond to it. This often indicates a permissions issue.

404 Not Found - The requested resource could not be found but may be available again in the future. This could be a broken link or incorrect URL.

405 Method Not Allowed - A request was made of a resource using a request method not supported by that resource.

406 Not Acceptable - The requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request.

407 Proxy Authentication Required - The client must first authenticate itself with the proxy.

408 Request Timeout - The server timed out waiting for the request.

409 Conflict - Indicates that the request could not be processed because of a conflict in the request, such as an edit conflict in the case of multiple updates.

410 Gone - Indicates that the resource requested is no longer available and will not be available again.

411 Length Required - The request did not specify the length of its content, which is required by the requested resource.

412 Precondition Failed - The server does not meet one of the preconditions that the requester put on the request.

413 Request Entity Too Large - The request is larger than the server is willing or able to process.

414 Request-URI Too Long - The URI provided was too long for the server to process.

415 Unsupported Media Type - The request entity has a media type which the server or resource does not support.

416 Requested Range Not Satisfiable - The client has asked for a portion of the file, but the server cannot supply that portion.

417 Expectation Failed - The server cannot meet the requirements of the Expect request-header field.

418 I'm a teapot - This code was defined in 1998 as one of the traditional IETF April Fools' jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers.

419 Authentication Timeout - Not a part of the HTTP standard, 419 Authentication Timeout denotes that previously valid authentication has expired.

420 Method Failure - Not part of the HTTP standard, but defined by Spring in the HttpStatus class to be used when a method failed.

420 Enhance Your Calm - Not part of the HTTP standard, but returned by version 1 of the Twitter Search and Trends API when the client is being rate limited.

422 Unprocessable Entity - The request was well-formed but was unable to be followed due to semantic errors.

423 Locked - The resource that is being accessed is locked.

424 Failed Dependency - The request failed due to failure of a previous request.

425 Unordered Collection - Defined in drafts of "WebDAV Advanced Collections Protocol", but not present in "Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol".

426 Upgrade Required - The client should switch to a different protocol such as TLS/1.0.

428 Precondition Required - The origin server requires the request to be conditional.

429 Too Many Requests - The user has sent too many requests in a given amount of time.

431 Request Header Fields Too Large - The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.

440 Login Timeout - A Microsoft extension. Indicates that your session has expired.

444 No Response - Used in Nginx logs to indicate that the server has returned no information to the client and closed the connection.

449 Retry With - A Microsoft extension. The request should be retried after performing the appropriate action.

450 Blocked by Windows Parental Controls - A Microsoft extension. This error is given when Windows Parental Controls are turned on and are blocking access to the given webpage.

451 Unavailable For Legal Reasons - Defined in the internet draft "A New HTTP Status Code for Legally-restricted Resources".

451 Redirect - Used in Exchange ActiveSync if there either is a more efficient server to use or the server cannot access the users' mailbox.

494 Request Header Too Large - Nginx internal code similar to 431 but it was introduced earlier.

495 Cert Error - Nginx internal code used when SSL client certificate error occurred to distinguish it from 4XX in a log and an error page redirection.

496 No Cert - Nginx internal code used when client didn't provide certificate to distinguish it from 4XX in a log and an error page redirection.

497 HTTP to HTTPS - Nginx internal code used for the plain HTTP requests that are sent to HTTPS port to distinguish it from 4XX in a log and an error page redirection.

499 Client Closed Request - Used in Nginx logs to indicate when the connection has been closed by client while the server is still processing its request, making server unable to send a status code back.

Server Errors (5xx) During Data Migration

Server errors indicate that the server