Skip to content

Commit f5969c7

Browse files
maxvpmaxvp
committed
Fix partial path
1 parent 742eb45 commit f5969c7

File tree

4 files changed

+42
-27
lines changed

4 files changed

+42
-27
lines changed

‎src/content/docs/cloudflare-one/policies/gateway/block-page.mdx‎

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -34,14 +34,11 @@ To turn on the block page and specify a custom block message:
3434
<Render
3535
file="gateway/add-block-page"
3636
params={{
37-
one: "Gateway > Firewall Policies > DNS or Gateway > Firewall Policies > HTTP",
37+
firewallPolicyPath:
38+
"**Gateway** > **Firewall policies** > **DNS** or **Gateway** > **Firewall policies** > **HTTP**",
3839
}}
3940
/>
4041

41-
## Troubleshoot the block page
42-
43-
If your users receive a security risk warning in their browser when visiting a blocked page, check that you have correctly [installed a Cloudflare certificate](/cloudflare-one/connections/connect-devices/user-side-certificates/manual-deployment/) on their devices.
44-
4542
## Customize the block page
4643

4744
<Render file="gateway/customize-block-page" />
@@ -63,3 +60,11 @@ You can add a Mailto link to your custom block page, which allows users to direc
6360
| User ID | The ID of the user who visited the page. Currently, User IDs are not surfaced in the dashboard and can only be viewed by calling the [API](/api/resources/zero_trust/subresources/access/subresources/users/methods/list/). |
6461
| Device ID | The ID of the device that visited the page. This is generated by the WARP client. |
6562
| Block Reason | Your policy-specific block message. |
63+
64+
## Limitations
65+
66+
If your users receive a security risk warning in their browser when visiting a blocked page, check that you have correctly [installed a Cloudflare certificate](/cloudflare-one/connections/connect-devices/user-side-certificates/manual-deployment/) on their devices.
67+
68+
If an HTTP request to be blocked does not arrive at the same Cloudflare data center as its DNS query, Gateway will display the default block page instead of your custom block page.
69+
70+
If the HTTP request comes from a different IP address from the DNS request, they cannot be correlated and the rule Id, custom message, and some other fields may be missing. This can happen when a recursive resolver source IP differs from the device IP

‎src/content/docs/learning-paths/cybersafe/gateway-onboarding/gateway-block-pages.mdx‎

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,16 +3,21 @@ title: Block pages
33
pcx_content_type: learning-unit
44
sidebar:
55
order: 7
6-
76
---
87

9-
import { Render } from "~/components"
8+
import { Render } from "~/components";
109

1110
## Enable the block page for DNS policies
1211

1312
For DNS policies, you will need to enable the block page on a per-policy basis.
1413

15-
<Render file="gateway/add-block-page" product="cloudflare-one" params={{ one: "Gateway > Firewall Policies > DNS" }} />
14+
<Render
15+
file="gateway/add-block-page"
16+
product="cloudflare-one"
17+
params={{
18+
firewallPolicyPath: "**Gateway** > **Firewall policies** > **DNS**",
19+
}}
20+
/>
1621

1722
## Customize the block page
1823

‎src/content/docs/learning-paths/replace-vpn/build-policies/block-page.mdx‎

Lines changed: 19 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -3,41 +3,46 @@ title: Gateway block page
33
pcx_content_type: overview
44
sidebar:
55
order: 5
6-
76
---
87

9-
import { Render } from "~/components"
8+
import { Render } from "~/components";
109

1110
With Cloudflare Zero Trust, you can deliver actionable feedback to users when they are blocked by a Gateway policy. Custom block messages can reduce user confusion and decrease your IT ticket load.
1211

1312
There are two different ways to surface block messages:
1413

15-
* [Custom block page](#custom-block-page)
16-
* [WARP client block notifications](#warp-client-block-notifications)
14+
- [Custom block page](#custom-block-page)
15+
- [WARP client block notifications](#warp-client-block-notifications)
1716

1817
## Custom block page
1918

2019
You can display a custom block page in the browser when users are blocked by a Gateway DNS or HTTP policy. This is a static page that educates users on why they were blocked and how to contact IT.
2120

2221
The custom block page has a few drawbacks:
2322

24-
* To display the block page, you must install a [user-side certificate](/learning-paths/replace-vpn/configure-device-agent/enable-tls-decryption/#configure-user-side-certificates) on the end user device.
25-
* You cannot customize the block message for individual DNS policies.
26-
* The block page does not appear when users are blocked by a Gateway network policy.
27-
* The custom block page only displays when the user loads a site in a browser. If, for instance, the user is allowed to visit a site but not allowed to upload a file, the file upload would fail silently and the user would not get a block page.
23+
- To display the block page, you must install a [user-side certificate](/learning-paths/replace-vpn/configure-device-agent/enable-tls-decryption/#configure-user-side-certificates) on the end user device.
24+
- You cannot customize the block message for individual DNS policies.
25+
- The block page does not appear when users are blocked by a Gateway network policy.
26+
- The custom block page only displays when the user loads a site in a browser. If, for instance, the user is allowed to visit a site but not allowed to upload a file, the file upload would fail silently and the user would not get a block page.
2827

2928
To work around these limitations, we recommend using [WARP client block notifications](#warp-client-block-notifications).
3029

3130
:::note
3231

33-
The Gateway custom block page is a different concept from [Access custom block pages](/cloudflare-one/applications/block-page/), which are used in conjunction with Cloudflare Access policies.
32+
The Gateway custom block page is a different concept from [Access custom block pages](/cloudflare-one/applications/block-page/), which are used in conjunction with Cloudflare Access policies.
3433
:::
3534

3635
### Enable the block page for DNS policies
3736

3837
For DNS policies, you will need to enable the block page on a per-policy basis.
3938

40-
<Render file="gateway/add-block-page" product="cloudflare-one" params={{ one: "Gateway > Firewall Policies > DNS" }} />
39+
<Render
40+
file="gateway/add-block-page"
41+
product="cloudflare-one"
42+
params={{
43+
firewallPolicyPath: "**Gateway** > **Firewall policies** > **DNS**",
44+
}}
45+
/>
4146

4247
### Customize the block page
4348

@@ -47,13 +52,13 @@ For DNS policies, you will need to enable the block page on a per-policy basis.
4752

4853
:::note
4954

50-
Only available on Enterprise plans.
55+
Only available on Enterprise plans.
5156
:::
5257

53-
For more granular user feedback, you can enable WARP client block notifications on any Gateway DNS or Network *Block* policy. Blocked users will receive an operating system notification from the WARP client with a custom message you set.
58+
For more granular user feedback, you can enable WARP client block notifications on any Gateway DNS or Network _Block_ policy. Blocked users will receive an operating system notification from the WARP client with a custom message you set.
5459

5560
Client notifications provide additional functionality over the [custom block page](#custom-block-page):
5661

57-
* Client notifications work with network policies, which means you can surface feedback for all partial actions on user traffic including blocking a specific port, file upload, or protocol.
62+
- Client notifications work with network policies, which means you can surface feedback for all partial actions on user traffic including blocking a specific port, file upload, or protocol.
5863

59-
* Client notifications allow you to direct users to a unique link per individual policy. For example, you could link users to your organization's acceptable use policy, data protection policy, or any existing IT troubleshooting infrastructure. If no infrastructure for this exists within your organization, you can quickly deploy an HTML site on [Cloudflare Pages](/pages/), put the site behind a [Cloudflare Access policy](/cloudflare-one/policies/access/), and provide dynamic feedback based on the identity and device posture values found in the user's [Access JWT](/cloudflare-one/identity/authorization-cookie/application-token/).
64+
- Client notifications allow you to direct users to a unique link per individual policy. For example, you could link users to your organization's acceptable use policy, data protection policy, or any existing IT troubleshooting infrastructure. If no infrastructure for this exists within your organization, you can quickly deploy an HTML site on [Cloudflare Pages](/pages/), put the site behind a [Cloudflare Access policy](/cloudflare-one/policies/access/), and provide dynamic feedback based on the identity and device posture values found in the user's [Access JWT](/cloudflare-one/identity/authorization-cookie/application-token/).

‎src/content/partials/cloudflare-one/gateway/add-block-page.mdx‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
2-
inputParameters: firewallPolicyPath
3-
2+
params:
3+
- firewallPolicyPath
44
---
55

6-
import { Markdown } from "~/components"
6+
import { Markdown } from "~/components";
77

8-
1. In [Zero Trust](https://one.dash.cloudflare.com), go to {props.one}.
8+
1. In [Zero Trust](https://one.dash.cloudflare.com), go to <Markdown text={props.firewallPolicyPath} />.
99
2. Find the policy you want to customize and select **Edit**. You can only edit the block page for policies with a Block action.
10-
3. Under **Configure policy settings**, go to **Display block page**. Choose *Show a custom message*.
10+
3. Under **Configure policy settings**, go to **Display block page**. Choose _Show a custom message_.
1111
4. In **Custom message**, enter a block message to show users.
1212
5. Select **Save policy**.
1313

0 commit comments

Comments
 (0)