cloudflare · zeinjaber · Feb 3, 2025 · Feb 3, 2025 · Feb 3, 2025 · pedrosousa
@@ -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
 

@@ -13,20 +13,38 @@ Implementation guides cover deployment steps and best practices for specific Clo
 
 <CardGrid>
 
-<LinkTitleCard title="Secure your Internet Traffic and SaaS apps" href="/learning-paths/secure-internet-traffic/" icon="seti:lock">
-	Provide your users and networks with a secure, performant, and flexible path to the Internet.
+<LinkTitleCard
+	title="Secure your Internet Traffic and SaaS apps"
+	href="/learning-paths/secure-internet-traffic/concepts/"
+	icon="seti:lock"
+>
+	Provide your users and networks with a secure, performant, and flexible path
+	to the Internet.
 </LinkTitleCard>
 
-<LinkTitleCard title="Replace your VPN" href="/learning-paths/secure-internet-traffic/" icon="seti:db">
+<LinkTitleCard
+	title="Replace your VPN"
+	href="/learning-paths/replace-vpn/concepts/"
+	icon="seti:db"
+>
 	Give users secure, auditable network and application access.
 </LinkTitleCard>
 
-<LinkTitleCard title="Deploy Zero Trust Web Access" href="/learning-paths/secure-internet-traffic/" icon="laptop">
+<LinkTitleCard
+	title="Deploy Zero Trust Web Access"
+	href="/learning-paths/zero-trust-web-access/concepts/"
+	icon="laptop"
+>
 	Secure access to internal web applications without a device client.
 </LinkTitleCard>
 
-<LinkTitleCard title="Secure Microsoft 365 email with Email Security" href="/learning-paths/secure-o365-email/" icon="email">
-	Use Cloudflare's Email Security to protect your Microsoft 365 email inbox from phishing and malware attacks.
+<LinkTitleCard
+	title="Secure Microsoft 365 email with Email Security"
+	href="/learning-paths/secure-o365-email/concepts/"
+	icon="email"
+>
+	Use Cloudflare's Email Security to protect your Microsoft 365 email inbox from
+	phishing and malware attacks.
 </LinkTitleCard>
 
-</CardGrid>
+</CardGrid>
@@ -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
 

@@ -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
 

@@ -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
 

@@ -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
 

@@ -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/).
+Cloudflare can handle 308 Permanent Redirects efficiently, ensuring redirection while maintaining request integrity. These redirects can be configured using [Redirect Rules](/rules/url-forwarding/).