diff --git a/src/content/docs/browser-rendering/index.mdx b/src/content/docs/browser-rendering/index.mdx index 6d9ba5d287d9323..5bf9262571faa2a 100644 --- a/src/content/docs/browser-rendering/index.mdx +++ b/src/content/docs/browser-rendering/index.mdx @@ -61,7 +61,11 @@ A globally distributed coordination API with strongly consistent storage. version of Puppeteer. - + New to Workers? Get started with the Workers Learning Path. diff --git a/src/content/docs/cache/troubleshooting/always-online.mdx b/src/content/docs/cache/troubleshooting/always-online.mdx index ac4abc52321aceb..5ff012710207cd6 100644 --- a/src/content/docs/cache/troubleshooting/always-online.mdx +++ b/src/content/docs/cache/troubleshooting/always-online.mdx @@ -28,7 +28,7 @@ There are limitations with the Always Online functionality: - Always Online has not initially crawled the website 2. Cloudflare cannot show private content behind logins or handle form submission (POSTs) if your origin web server is offline. -Always Online does not trigger for HTTP response codes such as [404](/support/troubleshooting/http-status-codes/4xx-client-error/#404-not-foundrfc7231), [503](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-503-service-temporarily-unavailable), or [500](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-500-internal-server-error) errors such as database connection errors or internal server errors. +Always Online does not trigger for HTTP response codes such as [404](/support/troubleshooting/http-status-codes/4xx-client-error/#404-not-found), [503](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-503-service-temporarily-unavailable), or [500](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-500-internal-server-error) errors such as database connection errors or internal server errors. ## Frequently asked questions diff --git a/src/content/docs/cloudflare-one/implementation-guides/index.mdx b/src/content/docs/cloudflare-one/implementation-guides/index.mdx index db0d2a648681abe..ecc057e8bbe6ffe 100644 --- a/src/content/docs/cloudflare-one/implementation-guides/index.mdx +++ b/src/content/docs/cloudflare-one/implementation-guides/index.mdx @@ -13,20 +13,38 @@ Implementation guides cover deployment steps and best practices for specific Clo - - Provide your users and networks with a secure, performant, and flexible path to the Internet. + + Provide your users and networks with a secure, performant, and flexible path + to the Internet. - + Give users secure, auditable network and application access. - + Secure access to internal web applications without a device client. - - Use Cloudflare's Email Security to protect your Microsoft 365 email inbox from phishing and malware attacks. + + Use Cloudflare's Email Security to protect your Microsoft 365 email inbox from + phishing and malware attacks. - \ No newline at end of file + diff --git a/src/content/docs/cloudflare-one/policies/data-loss-prevention/dlp-policies/logging-options.mdx b/src/content/docs/cloudflare-one/policies/data-loss-prevention/dlp-policies/logging-options.mdx index e503f833502d6d8..0beaa46bbe68dd0 100644 --- a/src/content/docs/cloudflare-one/policies/data-loss-prevention/dlp-policies/logging-options.mdx +++ b/src/content/docs/cloudflare-one/policies/data-loss-prevention/dlp-policies/logging-options.mdx @@ -5,7 +5,7 @@ sidebar: order: 2 --- -Data Loss Prevention allows you to capture, store, and view the data that triggered a specific DLP policy for use as forensic evidence. Users on all plans can [log the payload](#log-the-payload-of-matched-policies) of matched HTTP requests in their Cloudflare logs. Additionally, Enterprise users can [configure a Logpush job](#send-http-requests-to-logpush-destination) to send copies of entire matched HTTP requests to storage destinations. +Data Loss Prevention allows you to capture, store, and view the data that triggered a specific DLP policy for use as forensic evidence. Users on all plans can [log the payload](#log-the-payload-of-matched-rules) of matched HTTP requests in their Cloudflare logs. Additionally, Enterprise users can [configure a Logpush job](#send-http-requests-to-logpush-destination) to send copies of entire matched HTTP requests to storage destinations. ## Log the payload of matched rules diff --git a/src/content/docs/cloudflare-one/policies/gateway/block-page.mdx b/src/content/docs/cloudflare-one/policies/gateway/block-page.mdx index a5409aff47d8917..0bcf0888fa0834f 100644 --- a/src/content/docs/cloudflare-one/policies/gateway/block-page.mdx +++ b/src/content/docs/cloudflare-one/policies/gateway/block-page.mdx @@ -23,7 +23,7 @@ If your organization is still using the default Cloudflare certificate, you will ## Prerequisites -In order to display the block page as the URL of the blocked domain, your devices must have a [Cloudflare certificate](/cloudflare-one/connections/connect-devices/user-side-certificates/manual-deployment/) installed. Enterprise users can also [deploy their own root CA certificate](/cloudflare-one/connections/connect-devices/user-side-certificates/custom-certificate/). If you do not install a certificate, the block page [will not display correctly](#certificate-warning). +In order to display the block page as the URL of the blocked domain, your devices must have a [Cloudflare certificate](/cloudflare-one/connections/connect-devices/user-side-certificates/manual-deployment/) installed. Enterprise users can also [deploy their own root CA certificate](/cloudflare-one/connections/connect-devices/user-side-certificates/custom-certificate/). If you do not install a certificate, the block page [will not display correctly](#certificate-error). ## Turn on the block page diff --git a/src/content/docs/support/troubleshooting/http-status-codes/1xx-informational.mdx b/src/content/docs/support/troubleshooting/http-status-codes/1xx-informational.mdx index 81a27d55ce19773..4a927eae4de8c01 100644 --- a/src/content/docs/support/troubleshooting/http-status-codes/1xx-informational.mdx +++ b/src/content/docs/support/troubleshooting/http-status-codes/1xx-informational.mdx @@ -2,10 +2,9 @@ pcx_content_type: troubleshooting source: https://support.cloudflare.com/hc/en-us/articles/115003013892-1xx-Informational title: 1xx Informational - --- -The 1xx Informational status codes serve as interim responses that provide connection status updates without completing the request-response cycle. These codes are not intended for final actions but rather to indicate that the request is being processed or additional steps are required. +The 1xx Informational status codes serve as interim responses that provide connection status updates without completing the request-response cycle. These codes are not intended for final actions but rather to indicate that the request is being processed or additional steps are required. The requirements the server must follow when sending 1xx Informational status codes in response to a client's request include: @@ -16,7 +15,7 @@ Cloudflare forwards all 1xx responses from origin servers but does not generate ## 100 Continue -The 100 Continue status indicates that the server has received the request headers and is ready for the client to send the request body. For more information, refer to [RFC7231](https://tools.ietf.org/html/rfc7231). +The 100 Continue status indicates that the server has received the request headers and is ready for the client to send the request body. For more information, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). ### Common use cases @@ -30,7 +29,7 @@ Cloudflare uses Keep-Alive connections to maintain persistent communication betw ## 101 Switching Protocols -The 101 Switching Protocols status code indicates that the origin server accepts the client's request to switch protocols. For more information, refer to [RFC7231](https://tools.ietf.org/html/rfc7231). +The 101 Switching Protocols status code indicates that the origin server accepts the client's request to switch protocols. For more information, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). ### Common use cases @@ -42,11 +41,11 @@ Cloudflare supports WebSocket connections, which often involve the 101 Switching ## 102 Processing -102 Processing status code indicates that the server has received the request and is currently processing it, but the final response is not yet ready. This status code is only applicable to HTTP/1.1 and higher. For more information, refer to [RFC2518](https://tools.ietf.org/html/rfc2518). +102 Processing status code indicates that the server has received the request and is currently processing it, but the final response is not yet ready. This status code is only applicable to HTTP/1.1 and higher. For more information, refer to [RFC 2518](https://tools.ietf.org/html/rfc2518). ### Common use cases -The 102 Processing status code is commonly used in scenarios requiring long-running operations, such as complex database transactions or large file processing. It helps maintain the connection during extended processing times, typically exceeding 20 seconds, ensuring efficient communication between the client and server throughout the operation. +The 102 Processing status code is commonly used in scenarios requiring long-running operations, such as complex database transactions or large file processing. It helps maintain the connection during extended processing times, typically exceeding 20 seconds, ensuring efficient communication between the client and server throughout the operation. ### Cloudflare-specific information diff --git a/src/content/docs/support/troubleshooting/http-status-codes/2xx-success.mdx b/src/content/docs/support/troubleshooting/http-status-codes/2xx-success.mdx index 4e771311e2866b4..e5590b5fef26e1b 100644 --- a/src/content/docs/support/troubleshooting/http-status-codes/2xx-success.mdx +++ b/src/content/docs/support/troubleshooting/http-status-codes/2xx-success.mdx @@ -87,7 +87,7 @@ A 206 response includes either: - Partial payload that contains a `Content-Range` header specifying the requested range and the data provided in the response. - Multipart payload that omits the `Content-Range` header at the top level but includes `Content-Type` and `Content-Range` headers for each part of the multipart response body. -For more details, refer to [RFC 7233 Section 4.1](https://tools.ietf.org/html/rfc7233#page-10). +For more details, refer to [Section 4.1 of RFC 7233](https://tools.ietf.org/html/rfc7233#page-10). ### Cloudflare-specific information diff --git a/src/content/docs/support/troubleshooting/http-status-codes/3xx-redirection.mdx b/src/content/docs/support/troubleshooting/http-status-codes/3xx-redirection.mdx index d2d82f9bf5f542e..1b4ad1800be7168 100644 --- a/src/content/docs/support/troubleshooting/http-status-codes/3xx-redirection.mdx +++ b/src/content/docs/support/troubleshooting/http-status-codes/3xx-redirection.mdx @@ -2,7 +2,6 @@ pcx_content_type: troubleshooting source: https://support.cloudflare.com/hc/en-us/articles/115003011091-3xx-Redirection title: 3xx Redirection - --- 3xx codes are a class of responses which indicate that the HTTP client must take another course of action to obtain the complete requested resource. @@ -16,7 +15,7 @@ The redirect location should be specified in one of the following ways: The 300 Multiple Choices status indicates that multiple options are available for the requested resource, and the client may select one. -For more information, refer to [RFC7231](https://tools.ietf.org/html/rfc7231). +For more information, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). ### Common use cases @@ -30,14 +29,13 @@ The response may include a `Location` header pointing to a preferred option or p ### Cloudflare-specific information -Cloudflare generally bypasses the 300 Multiple Choices response for automated redirections to ensure optimal performance and user experience. - +Cloudflare generally bypasses the 300 Multiple Choices response for automated redirections to ensure optimal performance and user experience. ## 301 Moved Permanently The 301 Moved Permanently status indicates that the requested resource has been assigned a new permanent URI. All future references to this resource should use one of the enclosed URIs. -For more information, refer to [RFC7231](https://tools.ietf.org/html/rfc7231). +For more information, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). ### Common use cases @@ -53,13 +51,13 @@ The response typically includes a `Location` header specifying the new URI. This Cloudflare can generate 301 Moved Permanently responses without needing to query the origin server. For more information, refer to [Redirect Rules](/rules/url-forwarding/). -## 302 Found +## 302 Found The 302 Found status, also referred to as a temporary redirect, indicates that the requested resource is temporarily located at a different URI. Unlike a 301 Moved Permanently status, which denotes a permanent relocation, the 302 Found status is specifically intended for temporary use. While the User-Agent may follow the `Location` header to retrieve the resource, it should not replace the current URI as it would for a 301 Moved Permanently. -For more information, refer to [RFC7231](https://tools.ietf.org/html/rfc7231). +For more information, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). ### Common use cases @@ -77,7 +75,7 @@ Cloudflare can generate these responses, eliminating the need to send a request The 303 See Other status indicates that the client should retrieve the resource at a different URI using a `GET` request. Unlike a 301 Moved Permanently redirect, the resource at the redirect location is not necessarily equivalent to the originally requested resource. -For more information, refer to [RFC7231](https://tools.ietf.org/html/rfc7231). +For more information, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). ### Common use cases @@ -91,7 +89,7 @@ Cloudflare allows for the configuration of 303 redirects through [Redirect Rules ## 304 Not Modified -The 304 Not Modified status indicates that the requested resource is available and valid in the client's cache. This means that the origin server has not modified the resource since the client's last request, allowing the client to use the cached resource without connecting to the origin server again. Requirements for caches receiving a 304 response are defined in [Section 4.3.4 of \[RFC7234\]](https://tools.ietf.org/html/rfc7234#section-4.3.4). +The 304 Not Modified status indicates that the requested resource is available and valid in the client's cache. This means that the origin server has not modified the resource since the client's last request, allowing the client to use the cached resource without connecting to the origin server again. Requirements for caches receiving a 304 response are defined in [Section 4.3.4 of RFC 7234](https://tools.ietf.org/html/rfc7234#section-4.3.4). For more information, refer to [RFC 7232](https://tools.ietf.org/html/rfc7232). @@ -120,7 +118,7 @@ This status code indicates that subsequent requests should be sent through the s The 307 Temporary Redirect status indicates that a requested resource has been temporarily moved to a different URI, as specified in the `Location` header. Unlike a 302 redirect, the original request method (for example, `GET` or `POST`) must remain unchanged when the redirect is followed automatically. This ensures that temporary changes to a resource's location do not disrupt the intended behavior of the request. User agents may automatically follow the redirect using the `Location` header, but should not replace the original URI for future requests. -For more information, refer to [RFC7231](https://tools.ietf.org/html/rfc7231). +For more information, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). ### Common use cases @@ -142,4 +140,4 @@ The 308 Permanent Redirect status is commonly used for permanent resource reloca ### Cloudflare-specific information -Cloudflare can handle 308 Permanent Redirects efficiently, ensuring redirection while maintaining request integrity. These redirects can be configured using [Redirect Rules](/rules/url-forwarding/). \ No newline at end of file +Cloudflare can handle 308 Permanent Redirects efficiently, ensuring redirection while maintaining request integrity. These redirects can be configured using [Redirect Rules](/rules/url-forwarding/). 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 index 2eec8bfb70bd08f..9c4107db5741839 100644 --- 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 @@ -2,10 +2,9 @@ pcx_content_type: troubleshooting source: https://support.cloudflare.com/hc/en-us/articles/115003014512-4xx-Client-Error title: 4xx Client Error - --- -import { FeatureTable, Render } from "~/components" +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. @@ -17,7 +16,7 @@ import { FeatureTable, Render } from "~/components" 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 [RFC7231](https://tools.ietf.org/html/rfc7231). +For more information, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). ### Common use cases @@ -45,12 +44,12 @@ When encountering a `401` error while using the Cloudflare API, ensure that you ## 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 [RFC7231](https://tools.ietf.org/html/rfc7231). +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 clien'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 [RFC7231](https://tools.ietf.org/html/rfc7231). +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 @@ -67,12 +66,12 @@ 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/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors/). - - The [Browser Integrity Check](/waf/tools/browser-integrity-check/). - - [Validation Checks](/waf/analytics/security-events/additional-information/). + - [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/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors/). + - The [Browser Integrity Check](/waf/tools/browser-integrity-check/). + - [Validation Checks](/waf/analytics/security-events/additional-information/). 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: @@ -82,7 +81,7 @@ Cloudflare may also serve an unstyled `403` error page in specific cases. These 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 [RFC7231](https://tools.ietf.org/html/rfc7231). +For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). ### Common use cases @@ -98,7 +97,7 @@ Cloudflare does not generate `404s` for customer websites, we only proxy the req 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 [RFC7231](https://tools.ietf.org/html/rfc7231). +For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). ### Common use cases @@ -114,7 +113,7 @@ Cloudflare does not directly generate `405` errors. These errors are returned by 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 [RFC7231](https://tools.ietf.org/html/rfc7231)1. +For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). ### Common use cases @@ -141,7 +140,7 @@ Cloudflare does not generate `407` errors but proxies them from the origin serve 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 [RFC7231](https://tools.ietf.org/html/rfc7231). +For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). ### Common use cases @@ -153,11 +152,12 @@ Cloudflare does not generate `408` errors but may proxy them from the origin ser ## 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. +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 [RFC7231](https://tools.ietf.org/html/rfc7231). +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. @@ -169,13 +169,13 @@ Cloudflare will return a 409 response for a [Error 1001: DNS Resolution Error](/ ## 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. +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 [RFC7231](https://tools.ietf.org/html/rfc7231). +For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). ### Common use cases @@ -189,7 +189,7 @@ Cloudflare does not generate `410` for customer websites, we only proxy the requ 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 [RFC7231](https://tools.ietf.org/html/rfc7231). +For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). ### Common use cases @@ -217,7 +217,7 @@ Cloudflare may serve this response: for more information please refer to [ETag H 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 [RFC7231](https://tools.ietf.org/html/rfc7231). +For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). ### Common use cases @@ -235,7 +235,7 @@ If you require a larger upload, break up requests into smaller chunks, change yo 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 [RFC7231](https://tools.ietf.org/html/rfc7231). +For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). ### Common use cases @@ -249,7 +249,7 @@ Cloudflare will generate a `414` response if the URI length exceeds 32KB. 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 [RFC7231](https://tools.ietf.org/html/rfc7231). +For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). ### Common use cases @@ -263,7 +263,7 @@ Cloudflare typically passes this response from the origin server if it encounter 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 [RFC7233](https://datatracker.ietf.org/doc/html/rfc7233). +For more details, refer to [RFC 7233](https://datatracker.ietf.org/doc/html/rfc7233). ### Common use cases @@ -277,7 +277,7 @@ Cloudflare typically serves this response when the origin server rejects a `Rang 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 R[RFC7231](https://tools.ietf.org/html/rfc7231). +For more details, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231). ### Common use cases @@ -291,11 +291,11 @@ Cloudflare typically forwards this response from the origin server if it encount 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 [RFC6585](https://tools.ietf.org/html/rfc6585). +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. +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 @@ -311,11 +311,11 @@ Cloudflare will generate a `429` response when a request is being [rate limited] The `451` status code indicates that the server cannot deliver the requested resource due to legal actions or restrictions. -For more details, refer to [RFC7725](https://tools.ietf.org/html/rfc7725). +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. +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 @@ -349,4 +349,4 @@ 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. \ No newline at end of file +- **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/workers/index.mdx b/src/content/docs/workers/index.mdx index ffdd315019619b9..c6f9540bbcb2473 100644 --- a/src/content/docs/workers/index.mdx +++ b/src/content/docs/workers/index.mdx @@ -127,7 +127,11 @@ Offload third-party tools and services to the cloud and improve the speed and se - + New to Workers? Get started with the Workers Learning Path. diff --git a/src/pages/index.astro b/src/pages/index.astro index 903fd6e0fda0ae4..8793fcd47e30f6b 100644 --- a/src/pages/index.astro +++ b/src/pages/index.astro @@ -47,7 +47,7 @@ const topCards = [ { text: "Setup 1.1.1.1", href: "/1.1.1.1/setup/" }, { text: "Get started with Cloudflare", - href: "/learning-paths/get-started/", + href: "/learning-paths/get-started/concepts/", }, ], cta: { @@ -100,7 +100,10 @@ const topCards = [ text: "Browser Isolation", href: "/cloudflare-one/policies/browser-isolation/", }, - { text: "Replace your VPN", href: "/learning-paths/replace-vpn/" }, + { + text: "Replace your VPN", + href: "/learning-paths/replace-vpn/concepts/", + }, ], cta: { text: "View all Cloudflare One products",