Moves 4xx to separate pages (#22542)

Author: angelampcosta

src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error.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.

src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-400.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.

src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-401.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).

src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-403.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.

src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-404.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.

src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-405.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.

src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-406.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.

src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-407.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.

src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error/error-408.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/).