-
Notifications
You must be signed in to change notification settings - Fork 811
Suggestions for the Orange to Orange / custom Cloudflare configuration #7370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 1 commit
5ddda8f
b32684a
6b448ff
2d8a460
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -954,9 +954,12 @@ | |
|
|
||
| ### Can Cloudflare be used with Umbraco Cloud? | ||
|
|
||
| Yes. Since Umbraco Cloud already uses Cloudflare for DNS, hostnames must be enrolled as **DNS Only** with a CNAME pointing to `dns.umbraco.io`. Once the hostname appears as **Protected** in the **Project** > **Hostname** section, **Proxying** can be enabled in Cloudflare if specific features like Page Rules are required. | ||
| Yes. Hostnames managed in a customers CF zone can be be enrolled as **DNS Only** or by using [the hostname pre-validation flow](https://docs.umbraco.com/umbraco-cloud/go-live/manage-hostnames/hostname-pre-validation) in the [orange-to-orange configuration](https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/). | ||
|
Check warning on line 957 in umbraco-cloud/explore-umbraco-cloud/what-is-umbraco-cloud/frequently-asked-questions.md
|
||
|
|
||
| For optimal performance, keeping the DNS entry set to **DNS Only** in Cloudflare is recommended. This allows Umbraco Cloud to manage automatic Transport Layer Security (TLS)/HTTPS certificates for hostnames. Before implementing a custom Cloudflare setup, consult the support team via chat or [email](mailto:[email protected]). | ||
| - [Orange-to-orange configuration](https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) is the recommended approach for maximum control as you get to keep full control of you Edge configuration. In orange-to-orange configuration any Umbraco Cloud Cloudflare provided features such Managed Challenge, WAF can be stacked or disabled and managed manually in the customer zone. | ||
|
Check failure on line 959 in umbraco-cloud/explore-umbraco-cloud/what-is-umbraco-cloud/frequently-asked-questions.md
|
||
eshanrnh marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| - The **DNS Only** configuration is the recommended approach for minimum custom Cloudflare maintenance. In the **DNS Only** configuration the customers' Cloudflare zone won't apply DDoS protection or Web Application Firewall and the Umbraco Cloud Cloudflare features will continue working. | ||
eshanrnh marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| It is worth mentioning that Umbraco Cloud websites already provide many baseline Cloudflare features such as DDoS or Web Application Firewall by default. | ||
|
|
||
| ### Does Cloudflare add additional HTTP request headers? | ||
|
|
||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.