Skip to content

Commit bd3425c

Browse files
committed
Add configure section
1 parent 314e6da commit bd3425c

File tree

2 files changed

+43
-36
lines changed

2 files changed

+43
-36
lines changed

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

Lines changed: 41 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -23,40 +23,14 @@ If your organization is still using the default Cloudflare certificate, you will
2323

2424
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).
2525

26-
## Turn on the block page
27-
28-
For all HTTP Block policies, Gateway automatically displays a generic Cloudflare block page. For DNS Block policies, you will need to turn on the block page on a per-policy basis.
29-
30-
To turn on the block page for a policy:
31-
32-
<Tabs>
33-
34-
<TabItem label="DNS policy">
26+
## Configure the block page
3527

36-
<Render
37-
file="gateway/add-block-page"
38-
params={{
39-
firewallPolicyPath: "**Gateway** > **Firewall policies** > **DNS**",
40-
blockBehaviorAction: "turn on",
41-
}}
42-
/>
28+
To configure the block page:
4329

44-
</TabItem>
45-
<TabItem label="HTTP policy">
46-
47-
<Render
48-
file="gateway/add-block-page"
49-
params={{
50-
firewallPolicyPath: "**Gateway** > **Firewall policies** > **HTTP**",
51-
blockBehaviorAction: "go to",
52-
}}
53-
/>
54-
55-
</TabItem>
56-
57-
</Tabs>
30+
1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **Custom Pages**.
31+
2. Under **Account Gateway block page**, select **Customize**.
5832

59-
## Redirect to a block page
33+
### Redirect to a block page
6034

6135
Instead of displaying the Cloudflare block page, you can configure Gateway to return a `307` (Temporary Redirect) HTTP response code and redirect to a custom URL.
6236

@@ -69,15 +43,15 @@ To redirect users to a non-Cloudflare block page:
6943

7044
Gateway will now redirect users to a custom page when user traffic matches a Block policy with the block page configured.
7145

72-
## Customize the block page
46+
### Customize the block page
7347

7448
<Render file="gateway/customize-block-page" />
7549

76-
### Add a logo image
50+
#### Add a logo image
7751

7852
<Render file="gateway/add-logo-image" />
7953

80-
### Allow users to email an administrator
54+
#### Allow users to email an administrator
8155

8256
You can add a Mailto link to your custom block page, which allows users to directly email you about the blocked site. When users select **Contact your Administrator** on your block page, an email template opens with the email address and subject line you configure, as well as the following diagnostic information:
8357

@@ -91,6 +65,39 @@ You can add a Mailto link to your custom block page, which allows users to direc
9165
| Device ID | The ID of the device that visited the page. This is generated by the WARP client. |
9266
| Block Reason | Your policy-specific block message. |
9367

68+
## Turn on the block page
69+
70+
For DNS Block policies, you will need to turn on the block page for each policy. For HTTP Block policies, Gateway automatically displays your global block page setting by default. You can override the global setting for HTTP policies on a per-policy basis.
71+
72+
To turn on the block page for an individual policy:
73+
74+
<Tabs>
75+
76+
<TabItem label="DNS policy">
77+
78+
<Render
79+
file="gateway/add-block-page"
80+
params={{
81+
firewallPolicyPath: "**Gateway** > **Firewall policies** > **DNS**",
82+
blockBehaviorAction: "turn on",
83+
}}
84+
/>
85+
86+
</TabItem>
87+
<TabItem label="HTTP policy">
88+
89+
<Render
90+
file="gateway/add-block-page"
91+
params={{
92+
firewallPolicyPath: "**Gateway** > **Firewall policies** > **HTTP**",
93+
blockBehaviorAction: "go to",
94+
}}
95+
/>
96+
97+
</TabItem>
98+
99+
</Tabs>
100+
94101
## Limitations
95102

96103
### Certificate error

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,8 @@ import { Markdown } from "~/components";
1010
2. Select **Add a policy** to create a new policy, or choose the policy you want to customize and select **Edit**. You can only edit the block page for policies with a Block action.
1111
3. Under **Configure policy settings**, {props.blockBehaviorAction} **Modify Gateway block behavior**.
1212
4. Choose your block behavior:
13-
- **Use account-level block setting**: Use the global block page setting configured in your account settings. This can be either an [HTTP redirect](/cloudflare-one/policies/gateway/block-page/#redirect-to-a-block-page) or a [custom Cloudflare block page](/cloudflare-one/policies/gateway/block-page/#customize-the-block-page).
13+
- **Use account-level block setting**: Use the global block page setting configured in your account settings. The global setting can be either an [HTTP redirect](/cloudflare-one/policies/gateway/block-page/#redirect-to-a-block-page) or a [custom Cloudflare block page](/cloudflare-one/policies/gateway/block-page/#customize-the-block-page).
1414
- **Override account setting with URL redirect**: Redirect users with a `307` HTTP redirect to a URL you specify on a policy level.
1515
5. Select **Save policy**.
1616

17-
Gateway will display a custom message in your users' browsers when they are blocked by this policy.
17+
Depending on your settings, Gateway will display a block page in your users' browsers or redirect them to a specified URL when they are blocked by this policy.

0 commit comments

Comments
 (0)