You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/cache/troubleshooting/always-online.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ There are limitations with the Always Online functionality:
28
28
- Always Online has not initially crawled the website
29
29
2. Cloudflare cannot show private content behind logins or handle form submission (POSTs) if your origin web server is offline.
30
30
31
-
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.
31
+
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.
Copy file name to clipboardExpand all lines: src/content/docs/cloudflare-one/policies/data-loss-prevention/dlp-policies/logging-options.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ sidebar:
5
5
order: 2
6
6
---
7
7
8
-
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.
8
+
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.
Copy file name to clipboardExpand all lines: src/content/docs/cloudflare-one/policies/gateway/block-page.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ If your organization is still using the default Cloudflare certificate, you will
23
23
24
24
## Prerequisites
25
25
26
-
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).
26
+
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).
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.
7
+
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.
9
8
10
9
The requirements the server must follow when sending 1xx Informational status codes in response to a client's request include:
11
10
@@ -16,7 +15,7 @@ Cloudflare forwards all 1xx responses from origin servers but does not generate
16
15
17
16
## 100 Continue
18
17
19
-
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).
18
+
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).
20
19
21
20
### Common use cases
22
21
@@ -30,7 +29,7 @@ Cloudflare uses Keep-Alive connections to maintain persistent communication betw
30
29
31
30
## 101 Switching Protocols
32
31
33
-
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).
32
+
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).
34
33
35
34
### Common use cases
36
35
@@ -42,11 +41,11 @@ Cloudflare supports WebSocket connections, which often involve the 101 Switching
42
41
43
42
## 102 Processing
44
43
45
-
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).
44
+
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).
46
45
47
46
### Common use cases
48
47
49
-
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.
48
+
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.
Copy file name to clipboardExpand all lines: src/content/docs/support/troubleshooting/http-status-codes/2xx-success.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,7 +87,7 @@ A 206 response includes either:
87
87
- Partial payload that contains a `Content-Range` header specifying the requested range and the data provided in the response.
88
88
- 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.
89
89
90
-
For more details, refer to [RFC 7233 Section 4.1](https://tools.ietf.org/html/rfc7233#page-10).
90
+
For more details, refer to [Section 4.1 of RFC 7233](https://tools.ietf.org/html/rfc7233#page-10).
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:
16
15
17
16
The 300 Multiple Choices status indicates that multiple options are available for the requested resource, and the client may select one.
18
17
19
-
For more information, refer to [RFC7231](https://tools.ietf.org/html/rfc7231).
18
+
For more information, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231).
20
19
21
20
### Common use cases
22
21
@@ -30,14 +29,13 @@ The response may include a `Location` header pointing to a preferred option or p
30
29
31
30
### Cloudflare-specific information
32
31
33
-
Cloudflare generally bypasses the 300 Multiple Choices response for automated redirections to ensure optimal performance and user experience.
34
-
32
+
Cloudflare generally bypasses the 300 Multiple Choices response for automated redirections to ensure optimal performance and user experience.
35
33
36
34
## 301 Moved Permanently
37
35
38
36
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.
39
37
40
-
For more information, refer to [RFC7231](https://tools.ietf.org/html/rfc7231).
38
+
For more information, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231).
41
39
42
40
### Common use cases
43
41
@@ -53,13 +51,13 @@ The response typically includes a `Location` header specifying the new URI. This
53
51
54
52
Cloudflare can generate 301 Moved Permanently responses without needing to query the origin server. For more information, refer to [Redirect Rules](/rules/url-forwarding/).
55
53
56
-
## 302 Found
54
+
## 302 Found
57
55
58
56
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.
59
57
60
58
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.
61
59
62
-
For more information, refer to [RFC7231](https://tools.ietf.org/html/rfc7231).
60
+
For more information, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231).
63
61
64
62
### Common use cases
65
63
@@ -77,7 +75,7 @@ Cloudflare can generate these responses, eliminating the need to send a request
77
75
78
76
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.
79
77
80
-
For more information, refer to [RFC7231](https://tools.ietf.org/html/rfc7231).
78
+
For more information, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231).
81
79
82
80
### Common use cases
83
81
@@ -91,7 +89,7 @@ Cloudflare allows for the configuration of 303 redirects through [Redirect Rules
91
89
92
90
## 304 Not Modified
93
91
94
-
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).
92
+
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).
95
93
96
94
For more information, refer to [RFC 7232](https://tools.ietf.org/html/rfc7232).
97
95
@@ -120,7 +118,7 @@ This status code indicates that subsequent requests should be sent through the s
120
118
121
119
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.
122
120
123
-
For more information, refer to [RFC7231](https://tools.ietf.org/html/rfc7231).
121
+
For more information, refer to [RFC 7231](https://tools.ietf.org/html/rfc7231).
124
122
125
123
### Common use cases
126
124
@@ -142,4 +140,4 @@ The 308 Permanent Redirect status is commonly used for permanent resource reloca
142
140
143
141
### Cloudflare-specific information
144
142
145
-
Cloudflare can handle 308 Permanent Redirects efficiently, ensuring redirection while maintaining request integrity. These redirects can be configured using [Redirect Rules](/rules/url-forwarding/).
143
+
Cloudflare can handle 308 Permanent Redirects efficiently, ensuring redirection while maintaining request integrity. These redirects can be configured using [Redirect Rules](/rules/url-forwarding/).
0 commit comments