diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error.mdx deleted file mode 100644 index 8078dec3c76450..00000000000000 --- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error.mdx +++ /dev/null @@ -1,353 +0,0 @@ ---- -pcx_content_type: troubleshooting -source: https://support.cloudflare.com/hc/en-us/articles/115003014512-4xx-Client-Error -title: 4xx Client Error -description: Explore detailed explanations of 4xx client error codes, including causes and solutions, in Cloudflare's technical documentation for developers. ---- - -import { FeatureTable, Render } from "~/components"; - -`4xx` codes are error responses that indicate an issue on the client's end, potentially due to a network problem. - -- `4xx` codes can be used as a response to any request method. -- The origin server should include an explanation, which should be displayed by the User-Agent, except in the case of a `HEAD` request. -- [Custom rules](/waf/custom-rules/) can return any response code in the range of `400–499` on your HTML page if the site owner has created a rule with the _Block_ action and configured a custom response code. For more details, refer to [custom response](/waf/custom-rules/create-dashboard/#configure-a-custom-response-for-blocked-requests). - -## 400 Bad Request - -This error indicates that the client sent a request to the server that could not be understood or processed due to issues with the request itself. - -For more information, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). - -### Common use cases - -A `400 Bad Request` error occurs due to client-side issues, such as malformed request syntax, invalid request content, message framing problems, or deceptive request routing. For example, if the request contains a special character that is not properly [URL Encoded (or percent-encoded)](https://en.wikipedia.org/wiki/Percent-encoding), an `HTTP Error 400` will be returned. - -### Cloudflare-specific information - -If you encounter an HTTP error while using the [Cloudflare API](/api/), make sure that you are using the correct syntax, parameters, and body for your API call. - -## 401 Unauthorized - -This error indicates that the request was not sent with the proper authentication credentials. The server requires authentication to process the request. - -For more details, refer to [RFC 7235](https://tools.ietf.org/html/rfc7235). - -### Common use cases - -A `401 Unauthorized` error occurs when the client fails to provide valid authentication credentials. The server responds with at least one challenge in the form of a `WWW-Authenticate` header field, as outlined in [section 4.1](https://datatracker.ietf.org/doc/html/rfc7235#section-4.1). - -If the client resends the request with the same credentials and the challenge remains unchanged, the server may return an entity to assist the client in identifying the correct credentials needed. - -### Cloudflare-specific information - -When encountering a `401` error while using the Cloudflare API, ensure that you are providing the correct authentication credentials (for example, [API tokens](/fundamentals/api/get-started/create-token/) or [keys](/fundamentals/api/get-started/ca-keys/)). Double-check that the credentials are active and properly formatted. If the error persists, refer to the `WWW-Authenticate` header in the response for guidance on resolving the issue. - -## 402 Payment Required - -The `402 Payment Required` status code is reserved for future use and is not yet implemented according to the standards outlined in [RFC 7231](https://tools.ietf.org/html/rfc7231). - -## 403 Forbidden - -The `403 Forbidden` status code indicates that the client's request was understood by the server but cannot be fulfilled due to insufficient permissions to access the requested resource. -For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). - -### Common use cases - -If you encounter a `403` error without the Cloudflare branding, this means that the error is being returned directly by the origin web server, not Cloudflare. This is typically related to permission rules set on your server. Common reasons for this error are: - -- Permission rules configured on the origin web server (for example, in an Apache `.htaccess` file). -- Mod_security rules. -- IP deny rules, such as blocking traffic from certain IP ranges. Make sure that [Cloudflare's IP ranges](https://www.cloudflare.com/ips) are not being blocked. - -### Cloudflare-specific information - -Cloudflare may serve `403` responses in the following scenarios: - -- **WAF rules**: The request violated a default WAF managed rule (enabled for all orange-clouded Cloudflare domains) or a custom WAF managed rule specific to your zone. For more information, refer to [WAF Managed Rules](/waf/managed-rules/). - -- **Security features**: A `403` response with Cloudflare branding in the response body may be triggered by: - - [WAF Custom or Managed Rules](/waf/) with the challenge or block action. - - [Security Level](/waf/tools/security-level/) settings, which default to Medium. - - [DDoS Protection](/ddos-protection/), which is enabled by default on zones onboarded to Cloudflare, IP applications onboarded to Spectrum, and IP Prefixes onboarded to Magic Transit. - - Most [1xxx Cloudflare error codes](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/). - - The [Browser Integrity Check](/waf/tools/browser-integrity-check/). - - [Validation Checks](/waf/tools/validation-checks/). - -Cloudflare may also serve an unstyled `403` error page in specific cases. These errors are not logged because they occur early in Cloudflare's infrastructure, before domain configuration is loaded. An example is: - -- [SNI](https://www.cloudflare.com/learning/ssl/what-is-sni/): A `403` error is returned when the client sends a host that does not match the SNI (Server Name Indication). - -## 404 Not Found - -The `404 Not Found` status code indicates that the origin server was unable to locate the requested resource. Typically, this means the host server could not find the resource. For a more permanent version of this error, the 410 Gone status code should be used. - -For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). - -### Common use cases - -These errors typically occur when someone mistypes a URL on your site, when there is a broken link from another page, when a page that previously existed is moved or removed, or there is an error when a search engine indexes your site. - -These errors typically account for approximately 3% of total page views for a typical site. However, they often go untracked by traditional analytics platforms, such as Google Analytics. To improve user experience, website owners usually implement a custom 404 page to be displayed when this error is generated. - -### Cloudflare-specific information - -Cloudflare does not generate `404s` for customer websites, we only proxy the request from the origin server. If you encounter a `404` error on a Cloudflare-powered site, the issue lies with the origin server. In such cases, contact your hosting provider for assistance. - -## 405 Method Not Allowed - -The 405 Method Not Allowed status code indicates that the origin server recognizes the requested resource but does not support the HTTP method used in the request. - -For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). - -### Common use cases - -This error typically occurs when the client uses an unsupported HTTP method to interact with a specific resource. The origin server must include an `Allow` header in the response, which lists the HTTP methods supported for that resource. - -For example, attempting a `POST` request on a resource that is unchangeable and only supports `GET` requests will result in a `405` error. - -### Cloudflare-specific information - -Cloudflare does not directly generate `405` errors. These errors are returned by the origin server when it does not allow the HTTP method used in the request. If you encounter a `405` error, review the configuration of your origin server to ensure the correct methods are enabled for the resource in question. - -## 406 Not Acceptable - -The `406 Not Acceptable` status code indicates that the requested resource is not available in a format that adheres to the content negotiation headers specified by the client (for example, `Accept-Charset` or `Accept-Language`). - -For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). - -### Common use cases - -For example, if a client requests content in a specific language or character set that the server does not support, this error will be generated. To avoid returning a `406` error, the server can instead serve the less preferred method to the client's User-Agent, rather than rejecting the request. - -### Cloudflare-specific information - -Cloudflare does not generate `406` errors directly but can proxy these responses from the origin server. If content negotiation issues occur, they are typically related to configurations at the origin server, such as language or character set settings. - -## 407 Authentication Required - -The `407 Proxy Authentication Required` status code indicates that the client did not provide the necessary authentication credentials to access the requested resource through a proxy server. -For more details, refer to [RFC 7235](https://tools.ietf.org/html/rfc7235). - -### Common use cases - -This error typically occurs in environments where a proxy server is used as an intermediary between the client and the target server. To resolve this, the client must include the appropriate `Proxy-Authorization` header in the request with valid credentials. - -### Cloudflare-specific information - -Cloudflare does not generate `407` errors but proxies them from the origin server or an upstream proxy. If a `407` error occurs on a Cloudflare-powered site, review the origin server's proxy configuration to ensure authentication requirements are properly set, and verify that the client is providing the required credentials. - -## 408 Request Timeout - -The `408 Request Timeout` status code indicates that the origin server did not receive the complete request within a reasonable time frame and does not wish to continue waiting for the connection. This response is not commonly used, as servers often prefer to use the "close" connection option to terminate idle connections - -For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). - -### Common use cases - -This error typically occurs when a client fails to send a complete request within the server's timeout period. Common scenarios include slow network connections, server overload or client-side delays to complete the request. - -### Cloudflare-specific information - -Cloudflare does not generate `408` errors but may proxy them from the origin server. If a `408` error occurs on a Cloudflare-powered site, it is essential to review the origin server's timeout settings and ensure that the server is not overloaded. Additionally, verify that the client's Internet connection is stable and that the request is being sent promptly. - -## 409 Conflict - -The `409 Conflict` status code indicates that the request could not be completed due to a conflict with the current state of the target resource. - -For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). - -### Common use cases - -This error typically happens with a `PUT` request when multiple clients are attempting to edit the same resource. To solve this issue: - - - The server should generate a payload that includes enough information for the client to recognize the source of the conflict. - - Clients should retry the request again after resolving the conflict. - -### Cloudflare-specific information - -Cloudflare will return a 409 response for a [Error 1001: DNS Resolution Error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1001/). - -## 410 Gone - -When a resource is intentionally and permanently removed, servers use the `410 Gone` status code to inform clients that the resource is no longer available. -In this case: - - - The server suggests that links referencing the resource should be removed. - - The server is not obligated to use this status code instead of a `404` response, nor is it required to maintain this response for any specific period of time. - -For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). - -### Common use cases - -This status is commonly applied to deprecated content, such as outdated pages or discontinued products. - -### Cloudflare-specific information - -Cloudflare does not generate `410` for customer websites, we only proxy the request from the origin server. If you encounter a `410` error on a Cloudflare-powered site, the issue lies with the origin server. In such cases, contact your hosting provider for assistance. - -## 411 Length Required - -The `411 Length Required` status code indicates that the client did not specify the `Content-Length` of the request body in the headers, and this information is required to obtain the resource. The client may resend the request after adding the required header field. - -For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). - -### Common use cases - -This status code can occur in various scenarios, such as when a client sends an API request without the required `Content-Length` header, when uploading a file where the server needs the header to allocate resources, or when proxies or legacy systems enforce strict HTTP compliance. In each case, the server or intermediary requires the `Content-Length` header to process the request properly. - -### Cloudflare-specific information - -Cloudflare does not generate `411` for customer websites, we only proxy the request from the origin server. If you encounter a `411` error on a Cloudflare-powered site, the issue lies with the origin server. In such cases, contact your hosting provider for assistance. - -## 412 Precondition Failed - -The `412 Precondition Failed` status code indicates that the server denies the request because the resource does not meet the conditions specified by the client. - -For more details, refer to [RFC 7232](https://tools.ietf.org/html/rfc7232). - -### Common use cases - -One common use case for the `412 Precondition Failed` status code is version control. For example, a client modifying an existing resource may set the `If-Unmodified-Since` header to ensure the resource has not been changed since the client downloaded it for editing. If another client edits the resource after the specified date but before the original client uploads their changes, the server will return a `412` response to prevent overwriting the newer updates. - -### Cloudflare-specific information - -Cloudflare may serve this response: for more information please refer to [ETag Headers](/cache/reference/etag-headers/). - -## 413 Payload Too Large - -The `413 Payload Too Large` status code indicates that the server refuses to process the request because the payload sent by the client exceeds the server's acceptable size limit. The server may optionally close the connection. If this refusal would only happen temporarily, then the server should send a `Retry-After` header to specify when the client should try the request again. - -For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). - -### Common use cases - -The `413 Payload Too Large` status code often occurs when clients attempt to upload large files, such as videos or images, or send oversized request bodies, like JSON or XML payloads, that exceed the server's size limits. This can also happen during file transfers or API requests involving large datasets, prompting the server to reject the request. - -### Cloudflare-specific information - -The upload limit for the Cloudflare API depends on your plan. If you exceed this limit, your API call will receive a `413 Request Entity Too Large` error. - - - -If you require a larger upload, break up requests into smaller chunks, change your DNS record to [DNS-only](/dns/proxy-status/#dns-only-records), or [upgrade your plan](/fundamentals/subscriptions-and-billing/change-plan/). - -## 414 URI Too Long - -The `414 URI Too Long` status code indicates that the server refuses to process the request because the URI provided by the client is excessively long. - -For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). - -### Common use cases - -For example, if a client is attempting a `GET` request with an unusually long URI, such as one containing an excessive number of query parameters, after a `POST`, this could be seen as a security risk and a `414` is generated. - -### Cloudflare-specific information - -Cloudflare will generate a `414` response if the URI length exceeds 32KB. - -## 415 Unsupported Media Type - -The `415 Unsupported Media Type` status code indicates that the server refuses to process the request because the format of the payload is not supported. One way to identify and fix this issue would be to look at the `Content-Type` or `Content-Encoding` headers sent in the client's request. - -For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). - -### Common use cases - -This may be triggered by submitting a file type or format that the server is not configured to handle, such as uploading an unsupported image or document format, may also trigger this error. - -### Cloudflare-specific information - -Cloudflare typically passes this response from the origin server if it encounters an unsupported media type in the client's request payload. - -## 416 Range Not Satisfiable - -The `416 Range Not Satisfiable` status code indicates that the server cannot fulfill the requested range specified in the `Range` header of the client's request. - -For more details, refer to [RFC 7233](https://datatracker.ietf.org/doc/html/rfc7233). - -### Common use cases - -This error can happen when a client requests a byte range outside the bounds of the resource, such as a range exceeding the file's total size. It can also happen if the server does not support partial content delivery or if there is a conflict between the requested range and the server's understanding of the resource, often caused by an outdated or invalid cache. - -### Cloudflare-specific information - -Cloudflare typically serves this response when the origin server rejects a `Range` header request for a resource. This often occurs if the requested range exceeds the size of the file, as indicated in the `Content-Range` header. - -## 417 Expectation Failed - -The `417 Expectation Failed` status code indicates that the server could not meet the requirements specified in the `Expect` header of the client's request. - -For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). - -### Common use cases - -Some clients use the `Expect` header, such as `Expect: 100-continue`, to verify if the server is ready to receive a large payload, and if the server cannot fulfill this expectation, it returns a 417 response. Similarly, a server may reject a request with this error if the client includes an `Expect` header with unsupported or invalid values. - -### Cloudflare-specific information - -Cloudflare typically forwards this response from the origin server if it encounters an issue related to unsupported or unfulfilled `Expect` headers in the client's request. - -## 429 Too Many Requests - -The `429 Too Many Requests` status code indicates that the client has sent too many requests in a specified amount of time, as determined by the server's rate-limiting rules. The server may include a `Retry-After` header in the response to specify when the client can try again. - -For more details, refer to [RFC 6585](https://tools.ietf.org/html/rfc6585). - -### Common use cases - -Servers use this status code to prevent excessive API requests from overloading the system. For example, a client making repeated API calls within a short time frame may trigger a 429 response. Websites or services may impose rate limits to manage traffic spikes or prevent abuse, temporarily blocking excessive requests from users. - -### Cloudflare-specific information - -- **Cloudflare API limits** - - - -- **Website end users** - -Cloudflare will generate a `429` response when a request is being [rate limited](https://www.cloudflare.com/rate-limiting/). If visitors to your site encounter this error, it will be visible in the [Rate Limiting Analytics](/waf/reference/legacy/old-rate-limiting/#analytics) dashboard. - -## 451 Unavailable For Legal Reason - -The `451` status code indicates that the server cannot deliver the requested resource due to legal actions or restrictions. - -For more details, refer to [RFC 7725](https://tools.ietf.org/html/rfc7725). - -### Common use cases - -This occurs when access to a resource is blocked due to court orders, copyright claims, or other legal demands. Typically search engines (for example, Google) and ISP (for example, ATT) are the ones affected by this response code, rather than the origin server itself. The server should include an explanation in the response body, detailing the legal demand or reason for the restriction. - -### Cloudflare-specific information - -Cloudflare may pass through a `451` response from the origin server if the requested resource is legally restricted. - -## 499 Client Close Request - -The `HTTP 499` error typically occurs when a client terminates the connection before the server is able to respond. - -### Common use cases - -Examples of `499` errors include situations where a client times out and closes the connection before the server completes processing, such as during large file uploads or long-running requests. They can also occur due to issues in the TCP three-way handshake, where the client terminates the connection prematurely because of its timeout settings. - -### Cloudflare-specific information - -The `499 Client Closed Request` status code is specific to nginx and indicates that the client closed the connection while the server was still processing the request, preventing the server from sending a status code in response. This status code appears in [Cloudflare Logs](/logs/) and status code analytics for Enterprise customers. - -:::note -Since Cloudflare is built on nginx, the 499 HTTP code is also logged in Cloudflare Logs and analytics for connections terminated by clients before Cloudflare has finished processing the request. It is expected to occasionally see these entries in your logs as clients close connections. -::: - -To provide more context, a TCP connection must be established between Cloudflare and the website's origin server before any higher protocol (such as HTTP) begins communication. TCP uses a three-way handshake to establish connection: - -- **SYN**: Cloudflare sends a SYN packet to the origin server. -- **SYN+ACK**: The origin server responds with a SYN+ACK packet. -- **ACK**: Cloudflare sends an ACK packet back to the origin server. - -At this point, the connection is established, and both Cloudflare and the origin server can communicate. However, if the origin server does not send a SYN+ACK back to Cloudflare within 15 seconds, Cloudflare retries once more, with another 15-second timeout. - -Depending on the client-side timeout settings, the following scenarios can occur: - -- **Shorter client timeout (less than 30 seconds)**: If the client has a shorter timeout, it will abandon the connection before Cloudflare completes processing, and a `499` error will be logged. -- **Successful connection (more than 30 seconds)**: If the client has a longer timeout and the TCP connection is successfully established, the HTTP transaction proceeds normally, and Cloudflare returns a standard status code (`HTTP 200`). -- **Handshake failure**: If the client has a longer timeout but Cloudflare cannot establish the TCP handshake with the origin server, Cloudflare will return an `HTTP 522` status code. diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-400.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-400.mdx new file mode 100644 index 00000000000000..b58182e699bb70 --- /dev/null +++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-400.mdx @@ -0,0 +1,19 @@ +--- +pcx_content_type: troubleshooting +title: Error 400 +source: null +--- + +## 400 Bad Request + +This error indicates that the client sent a request to the server that could not be understood or processed due to issues with the request itself. + +For more information, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). + +### Common use cases + +A `400 Bad Request` error occurs due to client-side issues, such as malformed request syntax, invalid request content, message framing problems, or deceptive request routing. For example, if the request contains a special character that is not properly [URL Encoded (or percent-encoded)](https://en.wikipedia.org/wiki/Percent-encoding), an `HTTP Error 400` will be returned. + +### Cloudflare-specific information + +If you encounter an HTTP error while using the [Cloudflare API](/api/), make sure that you are using the correct syntax, parameters, and body for your API call. diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-401.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-401.mdx new file mode 100644 index 00000000000000..7e79c82cbcca5f --- /dev/null +++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-401.mdx @@ -0,0 +1,21 @@ +--- +pcx_content_type: troubleshooting +title: Error 401 +source: null +--- + +## 401 Unauthorized + +This error indicates that the request was not sent with the proper authentication credentials. The server requires authentication to process the request. + +For more details, refer to [RFC 7235](https://tools.ietf.org/html/rfc7235). + +### Common use cases + +A `401 Unauthorized` error occurs when the client fails to provide valid authentication credentials. The server responds with at least one challenge in the form of a `WWW-Authenticate` header field, as outlined in [section 4.1](https://datatracker.ietf.org/doc/html/rfc7235#section-4.1). + +If the client resends the request with the same credentials and the challenge remains unchanged, the server may return an entity to assist the client in identifying the correct credentials needed. + +### Cloudflare-specific information + +When encountering a `401` error while using the Cloudflare API, ensure that you are providing the correct authentication credentials (for example, [API tokens](/fundamentals/api/get-started/create-token/) or [keys](/fundamentals/api/get-started/ca-keys/)). Double-check that the credentials are active and properly formatted. If the error persists, refer to the `WWW-Authenticate` header in the response for guidance on resolving the issue. \ No newline at end of file diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-403.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-403.mdx new file mode 100644 index 00000000000000..6e426d52ff1fae --- /dev/null +++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-403.mdx @@ -0,0 +1,36 @@ +--- +pcx_content_type: troubleshooting +title: Error 403 +source: null +--- + +## 403 Forbidden + +The `403 Forbidden` status code indicates that the client's request was understood by the server but cannot be fulfilled due to insufficient permissions to access the requested resource. +For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). + +### Common use cases + +If you encounter a `403` error without the Cloudflare branding, this means that the error is being returned directly by the origin web server, not Cloudflare. This is typically related to permission rules set on your server. Common reasons for this error are: + +- Permission rules configured on the origin web server (for example, in an Apache `.htaccess` file). +- Mod_security rules. +- IP deny rules, such as blocking traffic from certain IP ranges. Make sure that [Cloudflare's IP ranges](https://www.cloudflare.com/ips) are not being blocked. + +### Cloudflare-specific information + +Cloudflare may serve `403` responses in the following scenarios: + +- **WAF rules**: The request violated a default WAF managed rule (enabled for all orange-clouded Cloudflare domains) or a custom WAF managed rule specific to your zone. For more information, refer to [WAF Managed Rules](/waf/managed-rules/). + +- **Security features**: A `403` response with Cloudflare branding in the response body may be triggered by: + - [WAF Custom or Managed Rules](/waf/) with the challenge or block action. + - [Security Level](/waf/tools/security-level/) settings, which default to Medium. + - [DDoS Protection](/ddos-protection/), which is enabled by default on zones onboarded to Cloudflare, IP applications onboarded to Spectrum, and IP Prefixes onboarded to Magic Transit. + - Most [1xxx Cloudflare error codes](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/). + - The [Browser Integrity Check](/waf/tools/browser-integrity-check/). + - [Validation Checks](/waf/tools/validation-checks/). + +Cloudflare may also serve an unstyled `403` error page in specific cases. These errors are not logged because they occur early in Cloudflare's infrastructure, before domain configuration is loaded. An example is: + +- [SNI](https://www.cloudflare.com/learning/ssl/what-is-sni/): A `403` error is returned when the client sends a host that does not match the SNI (Server Name Indication). diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-404.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-404.mdx new file mode 100644 index 00000000000000..f3ddb1ca584f06 --- /dev/null +++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-404.mdx @@ -0,0 +1,21 @@ +--- +pcx_content_type: troubleshooting +title: Error 404 +source: null +--- + +## 404 Not Found + +The `404 Not Found` status code indicates that the origin server was unable to locate the requested resource. Typically, this means the host server could not find the resource. For a more permanent version of this error, the 410 Gone status code should be used. + +For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). + +### Common use cases + +These errors typically occur when someone mistypes a URL on your site, when there is a broken link from another page, when a page that previously existed is moved or removed, or there is an error when a search engine indexes your site. + +These errors typically account for approximately 3% of total page views for a typical site. However, they often go untracked by traditional analytics platforms, such as Google Analytics. To improve user experience, website owners usually implement a custom 404 page to be displayed when this error is generated. + +### Cloudflare-specific information + +Cloudflare does not generate `404s` for customer websites, we only proxy the request from the origin server. If you encounter a `404` error on a Cloudflare-powered site, the issue lies with the origin server. In such cases, contact your hosting provider for assistance. diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-405.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-405.mdx new file mode 100644 index 00000000000000..d8a981000edf14 --- /dev/null +++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-405.mdx @@ -0,0 +1,21 @@ +--- +pcx_content_type: troubleshooting +title: Error 405 +source: null +--- + +## 405 Method Not Allowed + +The 405 Method Not Allowed status code indicates that the origin server recognizes the requested resource but does not support the HTTP method used in the request. + +For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). + +### Common use cases + +This error typically occurs when the client uses an unsupported HTTP method to interact with a specific resource. The origin server must include an `Allow` header in the response, which lists the HTTP methods supported for that resource. + +For example, attempting a `POST` request on a resource that is unchangeable and only supports `GET` requests will result in a `405` error. + +### Cloudflare-specific information + +Cloudflare does not directly generate `405` errors. These errors are returned by the origin server when it does not allow the HTTP method used in the request. If you encounter a `405` error, review the configuration of your origin server to ensure the correct methods are enabled for the resource in question. diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-406.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-406.mdx new file mode 100644 index 00000000000000..845a89e5ccdc76 --- /dev/null +++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-406.mdx @@ -0,0 +1,19 @@ +--- +pcx_content_type: troubleshooting +title: Error 406 +source: null +--- + +## 406 Not Acceptable + +The `406 Not Acceptable` status code indicates that the requested resource is not available in a format that adheres to the content negotiation headers specified by the client (for example, `Accept-Charset` or `Accept-Language`). + +For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). + +### Common use cases + +For example, if a client requests content in a specific language or character set that the server does not support, this error will be generated. To avoid returning a `406` error, the server can instead serve the less preferred method to the client's User-Agent, rather than rejecting the request. + +### Cloudflare-specific information + +Cloudflare does not generate `406` errors directly but can proxy these responses from the origin server. If content negotiation issues occur, they are typically related to configurations at the origin server, such as language or character set settings. \ No newline at end of file diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-407.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-407.mdx new file mode 100644 index 00000000000000..8fed05cedf967d --- /dev/null +++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-407.mdx @@ -0,0 +1,18 @@ +--- +pcx_content_type: troubleshooting +title: Error 407 +source: null +--- + +## 407 Authentication Required + +The `407 Proxy Authentication Required` status code indicates that the client did not provide the necessary authentication credentials to access the requested resource through a proxy server. +For more details, refer to [RFC 7235](https://tools.ietf.org/html/rfc7235). + +### Common use cases + +This error typically occurs in environments where a proxy server is used as an intermediary between the client and the target server. To resolve this, the client must include the appropriate `Proxy-Authorization` header in the request with valid credentials. + +### Cloudflare-specific information + +Cloudflare does not generate `407` errors but proxies them from the origin server or an upstream proxy. If a `407` error occurs on a Cloudflare-powered site, review the origin server's proxy configuration to ensure authentication requirements are properly set, and verify that the client is providing the required credentials. \ No newline at end of file diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-408.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-408.mdx new file mode 100644 index 00000000000000..5004569d73edfe --- /dev/null +++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-408.mdx @@ -0,0 +1,19 @@ +--- +pcx_content_type: troubleshooting +title: Error 408 +source: null +--- + +## 408 Request Timeout + +The `408 Request Timeout` status code indicates that the origin server did not receive the complete request within a reasonable time frame and does not wish to continue waiting for the connection. This response is not commonly used, as servers often prefer to use the "close" connection option to terminate idle connections + +For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). + +### Common use cases + +This error typically occurs when a client fails to send a complete request within the server's timeout period. Common scenarios include slow network connections, server overload or client-side delays to complete the request. + +### Cloudflare-specific information + +Cloudflare does not generate `408` errors but may proxy them from the origin server. If a `408` error occurs on a Cloudflare-powered site, it is essential to review the origin server's timeout settings and ensure that the server is not overloaded. Additionally, verify that the client's Internet connection is stable and that the request is being sent promptly. \ No newline at end of file diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-409.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-409.mdx new file mode 100644 index 00000000000000..61162d4e9b7dd4 --- /dev/null +++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-409.mdx @@ -0,0 +1,22 @@ +--- +pcx_content_type: troubleshooting +title: Error 409 +source: null +--- + +## 409 Conflict + +The `409 Conflict` status code indicates that the request could not be completed due to a conflict with the current state of the target resource. + +For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). + +### Common use cases + +This error typically happens with a `PUT` request when multiple clients are attempting to edit the same resource. To solve this issue: + + - The server should generate a payload that includes enough information for the client to recognize the source of the conflict. + - Clients should retry the request again after resolving the conflict. + +### Cloudflare-specific information + +Cloudflare will return a 409 response for a [Error 1001: DNS Resolution Error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1001/). \ No newline at end of file diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-410.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-410.mdx new file mode 100644 index 00000000000000..4c9c5ecc0fe217 --- /dev/null +++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-410.mdx @@ -0,0 +1,23 @@ +--- +pcx_content_type: troubleshooting +title: Error 410 +source: null +--- + +## 410 Gone + +When a resource is intentionally and permanently removed, servers use the `410 Gone` status code to inform clients that the resource is no longer available. +In this case: + + - The server suggests that links referencing the resource should be removed. + - The server is not obligated to use this status code instead of a `404` response, nor is it required to maintain this response for any specific period of time. + +For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). + +### Common use cases + +This status is commonly applied to deprecated content, such as outdated pages or discontinued products. + +### Cloudflare-specific information + +Cloudflare does not generate `410` for customer websites, we only proxy the request from the origin server. If you encounter a `410` error on a Cloudflare-powered site, the issue lies with the origin server. In such cases, contact your hosting provider for assistance. \ No newline at end of file diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-411.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-411.mdx new file mode 100644 index 00000000000000..ffa91739a7b556 --- /dev/null +++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-411.mdx @@ -0,0 +1,19 @@ +--- +pcx_content_type: troubleshooting +title: Error 411 +source: null +--- + +## 411 Length Required + +The `411 Length Required` status code indicates that the client did not specify the `Content-Length` of the request body in the headers, and this information is required to obtain the resource. The client may resend the request after adding the required header field. + +For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). + +### Common use cases + +This status code can occur in various scenarios, such as when a client sends an API request without the required `Content-Length` header, when uploading a file where the server needs the header to allocate resources, or when proxies or legacy systems enforce strict HTTP compliance. In each case, the server or intermediary requires the `Content-Length` header to process the request properly. + +### Cloudflare-specific information + +Cloudflare does not generate `411` for customer websites, we only proxy the request from the origin server. If you encounter a `411` error on a Cloudflare-powered site, the issue lies with the origin server. In such cases, contact your hosting provider for assistance. \ No newline at end of file diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-412.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-412.mdx new file mode 100644 index 00000000000000..db8b7da9a9b8b2 --- /dev/null +++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-412.mdx @@ -0,0 +1,19 @@ +--- +pcx_content_type: troubleshooting +title: Error 412 +source: null +--- + +## 412 Precondition Failed + +The `412 Precondition Failed` status code indicates that the server denies the request because the resource does not meet the conditions specified by the client. + +For more details, refer to [RFC 7232](https://tools.ietf.org/html/rfc7232). + +### Common use cases + +One common use case for the `412 Precondition Failed` status code is version control. For example, a client modifying an existing resource may set the `If-Unmodified-Since` header to ensure the resource has not been changed since the client downloaded it for editing. If another client edits the resource after the specified date but before the original client uploads their changes, the server will return a `412` response to prevent overwriting the newer updates. + +### Cloudflare-specific information + +Cloudflare may serve this response: for more information please refer to [ETag Headers](/cache/reference/etag-headers/). \ No newline at end of file diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-413.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-413.mdx new file mode 100644 index 00000000000000..08b3405b85530b --- /dev/null +++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-413.mdx @@ -0,0 +1,25 @@ +--- +pcx_content_type: troubleshooting +title: Error 413 +source: null +--- + +import { FeatureTable, Render } from "~/components"; + +## 413 Payload Too Large + +The `413 Payload Too Large` status code indicates that the server refuses to process the request because the payload sent by the client exceeds the server's acceptable size limit. The server may optionally close the connection. If this refusal would only happen temporarily, then the server should send a `Retry-After` header to specify when the client should try the request again. + +For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). + +### Common use cases + +The `413 Payload Too Large` status code often occurs when clients attempt to upload large files, such as videos or images, or send oversized request bodies, like JSON or XML payloads, that exceed the server's size limits. This can also happen during file transfers or API requests involving large datasets, prompting the server to reject the request. + +### Cloudflare-specific information + +The upload limit for the Cloudflare API depends on your plan. If you exceed this limit, your API call will receive a `413 Request Entity Too Large` error. + + + +If you require a larger upload, break up requests into smaller chunks, change your DNS record to [DNS-only](/dns/proxy-status/#dns-only-records), or [upgrade your plan](/fundamentals/subscriptions-and-billing/change-plan/). \ No newline at end of file diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-414.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-414.mdx new file mode 100644 index 00000000000000..7c00a37c6c062c --- /dev/null +++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-414.mdx @@ -0,0 +1,19 @@ +--- +pcx_content_type: troubleshooting +title: Error 414 +source: null +--- + +## 414 URI Too Long + +The `414 URI Too Long` status code indicates that the server refuses to process the request because the URI provided by the client is excessively long. + +For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). + +### Common use cases + +For example, if a client is attempting a `GET` request with an unusually long URI, such as one containing an excessive number of query parameters, after a `POST`, this could be seen as a security risk and a `414` is generated. + +### Cloudflare-specific information + +Cloudflare will generate a `414` response if the URI length exceeds 32KB. \ No newline at end of file diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-415.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-415.mdx new file mode 100644 index 00000000000000..b923f283f811e1 --- /dev/null +++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-415.mdx @@ -0,0 +1,19 @@ +--- +pcx_content_type: troubleshooting +title: Error 415 +source: null +--- + +## 415 Unsupported Media Type + +The `415 Unsupported Media Type` status code indicates that the server refuses to process the request because the format of the payload is not supported. One way to identify and fix this issue would be to look at the `Content-Type` or `Content-Encoding` headers sent in the client's request. + +For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). + +### Common use cases + +This may be triggered by submitting a file type or format that the server is not configured to handle, such as uploading an unsupported image or document format, may also trigger this error. + +### Cloudflare-specific information + +Cloudflare typically passes this response from the origin server if it encounters an unsupported media type in the client's request payload. diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-416.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-416.mdx new file mode 100644 index 00000000000000..9d3c3f5eedac8d --- /dev/null +++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-416.mdx @@ -0,0 +1,19 @@ +--- +pcx_content_type: troubleshooting +title: Error 416 +source: null +--- + +## 416 Range Not Satisfiable + +The `416 Range Not Satisfiable` status code indicates that the server cannot fulfill the requested range specified in the `Range` header of the client's request. + +For more details, refer to [RFC 7233](https://datatracker.ietf.org/doc/html/rfc7233). + +### Common use cases + +This error can happen when a client requests a byte range outside the bounds of the resource, such as a range exceeding the file's total size. It can also happen if the server does not support partial content delivery or if there is a conflict between the requested range and the server's understanding of the resource, often caused by an outdated or invalid cache. + +### Cloudflare-specific information + +Cloudflare typically serves this response when the origin server rejects a `Range` header request for a resource. This often occurs if the requested range exceeds the size of the file, as indicated in the `Content-Range` header. \ No newline at end of file diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-417.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-417.mdx new file mode 100644 index 00000000000000..c337ca62901419 --- /dev/null +++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-417.mdx @@ -0,0 +1,19 @@ +--- +pcx_content_type: troubleshooting +title: Error 417 +source: null +--- + +## 417 Expectation Failed + +The `417 Expectation Failed` status code indicates that the server could not meet the requirements specified in the `Expect` header of the client's request. + +For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). + +### Common use cases + +Some clients use the `Expect` header, such as `Expect: 100-continue`, to verify if the server is ready to receive a large payload, and if the server cannot fulfill this expectation, it returns a 417 response. Similarly, a server may reject a request with this error if the client includes an `Expect` header with unsupported or invalid values. + +### Cloudflare-specific information + +Cloudflare typically forwards this response from the origin server if it encounters an issue related to unsupported or unfulfilled `Expect` headers in the client's request. \ No newline at end of file diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-429.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-429.mdx new file mode 100644 index 00000000000000..98c6eb4cf114d7 --- /dev/null +++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-429.mdx @@ -0,0 +1,27 @@ +--- +pcx_content_type: troubleshooting +title: Error 429 +source: null +--- + +import { FeatureTable, Render } from "~/components"; + +## 429 Too Many Requests + +The `429 Too Many Requests` status code indicates that the client has sent too many requests in a specified amount of time, as determined by the server's rate-limiting rules. The server may include a `Retry-After` header in the response to specify when the client can try again. + +For more details, refer to [RFC 6585](https://tools.ietf.org/html/rfc6585). + +### Common use cases + +Servers use this status code to prevent excessive API requests from overloading the system. For example, a client making repeated API calls within a short time frame may trigger a 429 response. Websites or services may impose rate limits to manage traffic spikes or prevent abuse, temporarily blocking excessive requests from users. + +### Cloudflare-specific information + +- **Cloudflare API limits** + + + +- **Website end users** + +Cloudflare will generate a `429` response when a request is being [rate limited](https://www.cloudflare.com/rate-limiting/). If visitors to your site encounter this error, it will be visible in the [Rate Limiting Analytics](/waf/reference/legacy/old-rate-limiting/#analytics) dashboard. diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-451.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-451.mdx new file mode 100644 index 00000000000000..a6b8e3b49ce811 --- /dev/null +++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-451.mdx @@ -0,0 +1,19 @@ +--- +pcx_content_type: troubleshooting +title: Error 451 +source: null +--- + +## 451 Unavailable For Legal Reason + +The `451` status code indicates that the server cannot deliver the requested resource due to legal actions or restrictions. + +For more details, refer to [RFC 7725](https://tools.ietf.org/html/rfc7725). + +### Common use cases + +This occurs when access to a resource is blocked due to court orders, copyright claims, or other legal demands. Typically search engines (for example, Google) and ISP (for example, ATT) are the ones affected by this response code, rather than the origin server itself. The server should include an explanation in the response body, detailing the legal demand or reason for the restriction. + +### Cloudflare-specific information + +Cloudflare may pass through a `451` response from the origin server if the requested resource is legally restricted. \ No newline at end of file diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-499.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-499.mdx new file mode 100644 index 00000000000000..cbe7220644321d --- /dev/null +++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-499.mdx @@ -0,0 +1,35 @@ +--- +pcx_content_type: troubleshooting +title: Error 499 +source: null +--- + +## 499 Client Close Request + +The `HTTP 499` error typically occurs when a client terminates the connection before the server is able to respond. + +### Common use cases + +Examples of `499` errors include situations where a client times out and closes the connection before the server completes processing, such as during large file uploads or long-running requests. They can also occur due to issues in the TCP three-way handshake, where the client terminates the connection prematurely because of its timeout settings. + +### Cloudflare-specific information + +The `499 Client Closed Request` status code is specific to nginx and indicates that the client closed the connection while the server was still processing the request, preventing the server from sending a status code in response. This status code appears in [Cloudflare Logs](/logs/) and status code analytics for Enterprise customers. + +:::note +Since Cloudflare is built on nginx, the 499 HTTP code is also logged in Cloudflare Logs and analytics for connections terminated by clients before Cloudflare has finished processing the request. It is expected to occasionally see these entries in your logs as clients close connections. +::: + +To provide more context, a TCP connection must be established between Cloudflare and the website's origin server before any higher protocol (such as HTTP) begins communication. TCP uses a three-way handshake to establish connection: + +- **SYN**: Cloudflare sends a SYN packet to the origin server. +- **SYN+ACK**: The origin server responds with a SYN+ACK packet. +- **ACK**: Cloudflare sends an ACK packet back to the origin server. + +At this point, the connection is established, and both Cloudflare and the origin server can communicate. However, if the origin server does not send a SYN+ACK back to Cloudflare within 15 seconds, Cloudflare retries once more, with another 15-second timeout. + +Depending on the client-side timeout settings, the following scenarios can occur: + +- **Shorter client timeout (less than 30 seconds)**: If the client has a shorter timeout, it will abandon the connection before Cloudflare completes processing, and a `499` error will be logged. +- **Successful connection (more than 30 seconds)**: If the client has a longer timeout and the TCP connection is successfully established, the HTTP transaction proceeds normally, and Cloudflare returns a standard status code (`HTTP 200`). +- **Handshake failure**: If the client has a longer timeout but Cloudflare cannot establish the TCP handshake with the origin server, Cloudflare will return an `HTTP 522` status code. diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/index.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/index.mdx new file mode 100644 index 00000000000000..2e5c83be1d0bb4 --- /dev/null +++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/index.mdx @@ -0,0 +1,97 @@ +--- +pcx_content_type: troubleshooting +title: 4xx Client Error +source: null +--- + +`4xx` codes are error responses that indicate an issue on the client's end, potentially due to a network problem. + +- `4xx` codes can be used as a response to any request method. +- The origin server should include an explanation, which should be displayed by the User-Agent, except in the case of a `HEAD` request. +- [Custom rules](/waf/custom-rules/) can return any response code in the range of `400–499` on your HTML page if the site owner has created a rule with the _Block_ action and configured a custom response code. For more details, refer to [custom response](/waf/custom-rules/create-dashboard/#configure-a-custom-response-for-blocked-requests). + +## 400 Bad Request + +For a complete description of this error refer to the [Error 400](/support/troubleshooting/http-status-codes/4xx-client-error/error-400/) page. + +## 401 Unauthorized + +For a complete description of this error refer to the [Error 401](/support/troubleshooting/http-status-codes/4xx-client-error/error-401/) page. + + +## 402 Payment Required + +The `402 Payment Required` status code is reserved for future use and is not yet implemented according to the standards outlined in [RFC 7231](https://tools.ietf.org/html/rfc7231). + +## 403 Forbidden + +For a complete description of this error refer to the [Error 403](/support/troubleshooting/http-status-codes/4xx-client-error/error-403/) page. + + +## 404 Not Found + +For a complete description of this error refer to the [Error 404](/support/troubleshooting/http-status-codes/4xx-client-error/error-404/) page. + +## 405 Method Not Allowed + +For a complete description of this error refer to the [Error 405](/support/troubleshooting/http-status-codes/4xx-client-error/error-405/) page. + +## 406 Not Acceptable + +For a complete description of this error refer to the [Error 406](/support/troubleshooting/http-status-codes/4xx-client-error/error-406/) page. + +## 407 Authentication Required + +For a complete description of this error refer to the [Error 407](/support/troubleshooting/http-status-codes/4xx-client-error/error-407/) page. + +## 408 Request Timeout + +For a complete description of this error refer to the [Error 408](/support/troubleshooting/http-status-codes/4xx-client-error/error-408/) page. + +## 409 Conflict + +For a complete description of this error refer to the [Error 409](/support/troubleshooting/http-status-codes/4xx-client-error/error-409/) page. + +## 410 Gone + +For a complete description of this error refer to the [Error 410](/support/troubleshooting/http-status-codes/4xx-client-error/error-410/) page. + +## 411 Length Required + +For a complete description of this error refer to the [Error 411](/support/troubleshooting/http-status-codes/4xx-client-error/error-411/) page. + +## 412 Precondition Failed + +For a complete description of this error refer to the [Error 412](/support/troubleshooting/http-status-codes/4xx-client-error/error-412/) page. + +## 413 Payload Too Large + +For a complete description of this error refer to the [Error 413](/support/troubleshooting/http-status-codes/4xx-client-error/error-413/) page. + +## 414 URI Too Long + +For a complete description of this error refer to the [Error 414](/support/troubleshooting/http-status-codes/4xx-client-error/error-414/) page. + +## 415 Unsupported Media Type + +For a complete description of this error refer to the [Error 415](/support/troubleshooting/http-status-codes/4xx-client-error/error-415/) page. + +## 416 Range Not Satisfiable + +For a complete description of this error refer to the [Error 416](/support/troubleshooting/http-status-codes/4xx-client-error/error-416/) page. + +## 417 Expectation Failed + +For a complete description of this error refer to the [Error 417](/support/troubleshooting/http-status-codes/4xx-client-error/error-417/) page. + +## 429 Too Many Requests + +For a complete description of this error refer to the [Error 429](/support/troubleshooting/http-status-codes/4xx-client-error/error-429/) page. + +## 451 Unavailable For Legal Reason + +For a complete description of this error refer to the [Error 451](/support/troubleshooting/http-status-codes/4xx-client-error/error-451/) page. + +## 499 Client Close Request + +For a complete description of this error refer to the [Error 499](/support/troubleshooting/http-status-codes/4xx-client-error/error-499/) page. \ No newline at end of file diff --git a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors.mdx deleted file mode 100644 index 6c43acd7cfc3e3..00000000000000 --- a/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors.mdx +++ /dev/null @@ -1,238 +0,0 @@ ---- -pcx_content_type: troubleshooting -source: https://support.cloudflare.com/hc/en-us/articles/4425107232525-Troubleshooting-Cloudflare-10XXX-errors -title: Cloudflare 10XXX errors -description: Troubleshoot Cloudflare 10XXX errors with detailed solutions for common issues like duplicate list items, invalid URLs, and redirect conflicts. - ---- -## Error 10028: The add list items operation contains duplicate items - -This error indicates that the operation to add items to a list contains duplicate entries within the same request. - -### Common causes - -This error occurs when there are duplicate list items in a single operation to add items to a List (either an IP list or a Bulk Redirect List). This error can happen when you: - -- Add a repeated IP address to an IP list -- Add a repeated source URL to a Bulk Redirect List - -### Resolution - -You need to remove the duplicate item and try again. - -## Error 10043: Source URL in redirect is too long - -This error indicates that the source URL in a redirect exceeds the maximum allowed length. - -### Common causes - -This error occurs when the source URL value of a URL redirect is too long. The maximum length of a source URL is 32,768 characters. Possible causes of this error are: - -- Dynamic URLs that contain excessive query parameters or tracking codes. -- Unnecessary path segments or redundant subdirectories in the URL. - -### Resolution - -You need to use a shorter URL as the source URL. - -## Error 10044: Target URL in redirect is too long - -This error indicates that the target URL in a redirect exceeds the maximum allowed length. - -### Common causes - -This error occurs when the target URL value of a URL redirect is too long. The maximum length of a target URL is 32,768 characters. Possible causes of this error are: - -- Dynamic URLs that contain excessive query parameters or tracking codes. -- Unnecessary path segments or redundant subdirectories in the URL. - -### Resolution - -You need to use a shorter URL as the target URL. - -## Error 10045: Invalid redirect source URL - -This error indicates that the source URL for a redirect is not valid. - -### Common causes - -This error occurs when the source URL provided for a URL redirect is not valid, preventing the redirect from functioning properly due to missing components, such as the scheme (for instance, `http` or `https`) or improper formatting. - -### Resolution - -You need to specify a valid URL as the source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs. - -## Error 10046: Invalid redirect target URL - -This error indicates that the target URL provided for a URL redirect is not valid. - -### Common causes - -This error occurs when the target URL provided for a URL redirect is not valid, preventing the redirect from functioning properly due to missing components, such as the scheme (for instance, `http` or `https`) or improper formatting. - -### Resolution - -You need to specify a valid URL as the target URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect target URLs. - -## Error 10047: Invalid redirect status code - -This error indicates that an unsupported or incorrectly formatted status code was specified for the URL redirect. - -### Common causes - -This error occurs when you specify a URL redirect status code that is not supported, typically due to entering an invalid number or using an unsupported or deprecated status code. - -### Resolution - -Use one of the supported status codes in the URL redirect: `301`, `302`, `307`, or `308`. - -## Error 10048: Preserve path suffix requires subpath matching enabled - -This error indicates a configuration mismatch where the **Preserve path suffix** option is used without enabling **Subpath matching** in a URL redirect. - -### Common causes - -This error occurs when you enable the **Preserve path suffix** option in a redirect without enabling the **Subpath matching** option. The **Preserve path suffix** option of a URL redirect is only applicable when the **Subpath matching** option is also enabled. - -### Resolution - -Enable **Subpath matching** for the URL redirect with **Preserve path suffix** enabled. - -## Error 10049: Invalid scheme in redirect source URL - -This error indicates that the source URL's scheme is invalid. - -### Common causes - -This error occurs when the source URL of a URL redirect has an invalid scheme, which may be due to a misspelled or unsupported scheme or because the scheme is missing or improperly formatted. - -### Resolution - -Review the source URL and ensure that it uses one of the supported schemes: `http`, `https`, or empty (no scheme information, which means that it applies to both schemes). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs. - -## Error 10050: Invalid redirect source URL with user info - -This error indicates that the source URL includes unsupported user information. - -### Common causes - -This error occurs when the source URL of a URL redirect includes a user info component (for example, `https://user:password@example.com`), which is not supported. - -### Resolution - -You need to remove the user information component from the redirect source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs. - -## Error 10051: Missing authority in redirect source URL - -This error indicates that the source URL is missing a required authority component. - -### Common causes - -This error occurs when the source URL of a URL redirect does not include an authority component (for example, `http:///path`, without a hostname), which is mandatory. - -### Resolution - -Add an authority component to the redirect source URL (for example, include a hostname). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the required URL components for redirect source URLs. - -## Error 10052: Invalid redirect source URL with port - -This error indicates that the source URL includes an unsupported port. - -### Common causes - -This error occurs when the source URL of a URL redirect includes a port (for example, `https://example.com:8081`), which is not supported. Possible causes include using a custom or non-standard port, copying a URL from another environment that includes a port, or mistakenly using a development or testing URL. - -### Resolution - -Remove the port from the redirect source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs. - -## Error 10053: Invalid redirect source URL with query string - -This error indicates that the source URL contains an unsupported query string component. - -### Common causes - -This error occurs when the source URL of a URL redirect includes a query string component, which is not supported. Possible causes include copying a URL with query parameters, misconfiguration during setup, or attempting to redirect based on query parameters instead of the path. - -### Resolution - -Remove the query string from the redirect source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs. - -## Error 10054: Invalid redirect source URL with fragment - -This error indicates that the source URL includes an unsupported fragment component. - -### Common causes - -This error occurs when the source URL of a URL redirect includes a fragment component (for example, `https://example.com/search/#fragment`). Fragment components are not part of an HTTP request; they are an indication for the browser to scroll to a specific location once the page has loaded. Possible causes of this error include copying a URL with a fragment from a browser or external source, or inadvertently adding a fragment during URL configuration or editing. - -### Resolution - -Remove the fragment from the redirect source URL. Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the supported URL components for redirect source URLs. - -## Error 10055: Query string settings incompatible with redirect target URL - -This error indicates a conflict between the **Preserve query string** option and the query string in the redirect target URL. - -### Common causes - -This error occurs when you enable the **Preserve query string** option of a URL redirect, but also provide a query string in the redirect target URL. In this case, the URL redirect would have conflicting configuration on how to handle the query string of incoming requests. - -### Resolution - -To resolve this issue, either disable the **Preserve query string** option in the URL redirect or remove the query string component from the redirect target URL to eliminate the conflict. - -## Error 10056: The add list items operation contains different types of list items - -This error indicates that different types of list items were combined in a single add operation. - -### Common causes - -This error occurs when different types of list items (such as IP addresses, hostnames, and URL redirects) are included in a single operation to add items to a list. It can occur with an IP list, a hostname list, or a Bulk Redirect List. - -### Resolution - -Remove the list items that do not apply to the list type. This means: - -- Removing IP addresses from a request to add items to a Bulk Redirect List. -- Removing URL redirects from a request to add items to an IP list. - -## Error 10058: List items incompatible with list type - -This error indicates that incompatible items were added to the wrong list type. - -### Common causes - -This error occurs when you are adding items to a list (either IP list, hostname list, or Bulk Redirect List) and the list items are incompatible with the list type. - -### Resolution - -Make sure you are adding the items to the correct list: - -- Custom lists with IP addresses (IP lists) can only contain IP addresses as list items. -- Custom lists with hostnames can only contain hostnames as list items. -- Bulk Redirect Lists can only contain URL redirects as list items. - -## Error 10059: Maximum number of repeated URL source paths exceeded - -This error indicates that the same URL path is repeated too many times across your Bulk Redirect Lists. - -### Common causes - -This error occurs when you have more than the maximum number of URL redirects with the same source URL path across all Bulk Redirect Lists in your account, regardless of the URL redirect domain. Possible causes include multiple lists containing the same redirects, overlapping configurations, or mismanagement resulting in duplicated source URL paths. - -### Resolution - -Review the path of your source URLs so that you do not have more than the maximum number of URL redirects sharing the same URL path in your account, regardless of their domain or the list they belong to. Refer to [URL redirect parameters](/rules/url-forwarding/bulk-redirects/reference/parameters/) for more information on the current limits. - -## Error 10060: Missing scheme in redirect target URL - -This error indicates that the target URL is missing a scheme. - -### Common causes - -This error occurs when the target URL of a URL redirect does not include a scheme, which is mandatory. This could have happened due to a typo or the URL was copied from a source that did not include the scheme. - -### Resolution - -Review the target URL of the URL redirect and ensure that it contains a scheme (for example, `https`). Refer to [Supported URL components in Bulk Redirects](/rules/url-forwarding/bulk-redirects/reference/url-components/) for details on the required URL components for redirect target URLs.