mirror of
https://github.com/cloudflare/cloudflare-docs.git
synced 2026-01-16 23:11:06 +00:00
Farber/pcx 8382 2 (#10820)
* adding redirects and removing hugo alias tags * updating links across docs * fixing more links * disablign aliases
This commit is contained in:
parent
974a3b9f65
commit
0d31181bd6
300 changed files with 471 additions and 611 deletions
|
|
@ -109,7 +109,7 @@
|
|||
"title": "Get started with Cloudflare"
|
||||
},
|
||||
{
|
||||
"url_path": "/fundamentals/get-started/setup/add-site/",
|
||||
"url_path": "/fundamentals/setup/account-setup/add-site/",
|
||||
"title": "Add a site to Cloudflare"
|
||||
},
|
||||
{
|
||||
|
|
@ -174,7 +174,7 @@
|
|||
"title": "Solving 'Registry Status: Client transfer prohibited'"
|
||||
},
|
||||
{
|
||||
"url_path": "/fundamentals/get-started/setup/add-site/",
|
||||
"url_path": "/fundamentals/setup/account-setup/add-site/",
|
||||
"title": "Add a site to Cloudflare"
|
||||
},
|
||||
{
|
||||
|
|
@ -196,7 +196,7 @@
|
|||
"dashPath": "/:accountId/members",
|
||||
"recommendations": [
|
||||
{
|
||||
"url_path": "/fundamentals/account-and-billing/members/manage/",
|
||||
"url_path": "/fundamentals/setup/manage-members/manage/",
|
||||
"title": "Manage account members"
|
||||
},
|
||||
{
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ DefaultContentLanguage = "en"
|
|||
disableHugoGeneratorInject = true
|
||||
enableRobotsTXT = false
|
||||
summaryLength = 30
|
||||
disableAliases = false
|
||||
disableAliases = true
|
||||
disableKinds = ["taxonomy", "taxonomyTerm"]
|
||||
|
||||
enableEmoji = true
|
||||
|
|
|
|||
|
|
@ -271,15 +271,15 @@
|
|||
/email-routing/known-limitations/ /email-routing/postmaster/ 301
|
||||
|
||||
# firewall
|
||||
/firewall/api/cf-lists/ /fundamentals/global-configurations/lists/lists-api/ 301
|
||||
/firewall/api/cf-lists/endpoints/ /fundamentals/global-configurations/lists/lists-api/endpoints/ 301
|
||||
/firewall/api/cf-lists/json-object/ /fundamentals/global-configurations/lists/lists-api/json-object/ 301
|
||||
/firewall/api/cf-lists/ /waf/tools/lists/lists-api/ 301
|
||||
/firewall/api/cf-lists/endpoints/ /waf/tools/lists/lists-api/endpoints/ 301
|
||||
/firewall/api/cf-lists/json-object/ /waf/tools/lists/lists-api/json-object/ 301
|
||||
/firewall/cf-dashboard/edit-expressions/ /ruleset-engine/rules-language/expressions/edit-expressions/ 301
|
||||
/firewall/cf-dashboard/expression-preview-editor/ /ruleset-engine/rules-language/expressions/edit-expressions/ 301
|
||||
/firewall/cf-dashboard/rules-lists/ /fundamentals/global-configurations/lists/ip-lists/ 301
|
||||
/firewall/cf-dashboard/rules-lists/manage-items/ /fundamentals/global-configurations/lists/create-dashboard/#add-items-to-a-list 301
|
||||
/firewall/cf-dashboard/rules-lists/manage-lists/ /fundamentals/global-configurations/lists/create-dashboard/ 301
|
||||
/firewall/cf-dashboard/rules-lists/use-lists-in-expressions/ /fundamentals/global-configurations/lists/use-in-expressions/ 301
|
||||
/firewall/cf-dashboard/rules-lists/ /waf/tools/lists/ip-lists/ 301
|
||||
/firewall/cf-dashboard/rules-lists/manage-items/ /rules/url-forwarding/bulk-redirects/create-dashboard/#add-items-to-a-list 301
|
||||
/firewall/cf-dashboard/rules-lists/manage-lists/ /rules/url-forwarding/bulk-redirects/create-dashboard/ 301
|
||||
/firewall/cf-dashboard/rules-lists/use-lists-in-expressions/ /waf/tools/lists/use-in-expressions/ 301
|
||||
/firewall/cf-firewall-language/ /ruleset-engine/rules-language/ 301
|
||||
/firewall/cf-firewall-language/fields/ /ruleset-engine/rules-language/fields/ 301
|
||||
/firewall/cf-firewall-language/functions/ /ruleset-engine/rules-language/functions/ 301
|
||||
|
|
@ -287,7 +287,7 @@
|
|||
/firewall/cf-firewall-language/values/ /ruleset-engine/rules-language/values/ 301
|
||||
/firewall/cf-firewall-rules/api-shield/ /api-shield/ 301
|
||||
/firewall/cf-firewall-rules/fields-and-expressions/ /ruleset-engine/rules-language/expressions/ 301
|
||||
/firewall/cf-firewall-rules/rules-lists/ /fundamentals/global-configurations/lists/ip-lists/ 301
|
||||
/firewall/cf-firewall-rules/rules-lists/ /waf/tools/lists/ip-lists/ 301
|
||||
/firewall/cf-rulesets/ /ruleset-engine/about/ 301
|
||||
/firewall/cf-rulesets/add-rule-phase-rulesets/ /ruleset-engine/basic-operations/add-rule-phase-rulesets/ 301
|
||||
/firewall/cf-rulesets/common-use-cases/ /ruleset-engine/managed-rulesets/override-examples/ 301
|
||||
|
|
@ -325,19 +325,19 @@
|
|||
/support/page-rules/required-firewall-rule-changes-to-enable-url-normalization/ /firewall/troubleshooting/required-changes-to-enable-url-normalization/ 301
|
||||
|
||||
# fundamentals
|
||||
/fundamentals/account-and-billing/account-setup/account-roles/ /fundamentals/account-and-billing/members/roles/ 301
|
||||
/fundamentals/account-and-billing/account-setup/manage-account-members/ /fundamentals/account-and-billing/members/ 301
|
||||
/fundamentals/account-and-billing/account-setup/account-roles/ /fundamentals/setup/manage-members/roles/ 301
|
||||
/fundamentals/account-and-billing/account-setup/manage-account-members/ /fundamentals/setup/manage-members/ 301
|
||||
/fundamentals/account-and-billing/account-security/scim-setup/ /fundamentals/account-and-billing/account-security/ 301
|
||||
/fundamentals/get-started/cdn/ /fundamentals/get-started/concepts/how-cloudflare-works/ 301
|
||||
/fundamentals/get-started/how-cloudflare-works/ /fundamentals/get-started/concepts/how-cloudflare-works/ 301
|
||||
/fundamentals/get-started/cloudflare-cookies/ /fundamentals/get-started/reference/cloudflare-cookies/ 301
|
||||
/fundamentals/get-started/google-analytics/ /fundamentals/get-started/reference/google-analytics/ 301
|
||||
/fundamentals/get-started/http-request-headers/ /fundamentals/get-started/reference/http-request-headers/ 301
|
||||
/fundamentals/get-started/network-ports/ /fundamentals/get-started/reference/network-ports/ 301
|
||||
/fundamentals/get-started/basic-tasks/improve-seo/ /fundamentals/get-started/task-guides/improve-seo/ 301
|
||||
/fundamentals/get-started/basic-tasks/allow-cloudflare-ip-addresses/ /fundamentals/get-started/setup/allow-cloudflare-ip-addresses/ 301
|
||||
/fundamentals/get-started/basic-tasks/account-setup/ /fundamentals/account-and-billing/account-setup/ 301
|
||||
/fundamentals/get-started/concepts/cdn-cgi-endpoint/ /fundamentals/get-started/reference/cdn-cgi-endpoint/ 301
|
||||
/fundamentals/get-started/cdn/ /fundamentals/concepts/how-cloudflare-works/ 301
|
||||
/fundamentals/get-started/how-cloudflare-works/ /fundamentals/concepts/how-cloudflare-works/ 301
|
||||
/fundamentals/get-started/cloudflare-cookies/ /fundamentals/reference/policies-compliances/cloudflare-cookies/ 301
|
||||
/fundamentals/get-started/google-analytics/ /fundamentals/reference/google-analytics/ 301
|
||||
/fundamentals/get-started/http-request-headers/ /fundamentals/reference/http-request-headers/ 301
|
||||
/fundamentals/get-started/network-ports/ /fundamentals/reference/network-ports/ 301
|
||||
/fundamentals/get-started/basic-tasks/improve-seo/ /fundamentals/basic-tasks/improve-seo/ 301
|
||||
/fundamentals/get-started/basic-tasks/allow-cloudflare-ip-addresses/ /fundamentals/setup/allow-cloudflare-ip-addresses/ 301
|
||||
/fundamentals/get-started/basic-tasks/account-setup/ /fundamentals/setup/account-setup/ 301
|
||||
/fundamentals/get-started/concepts/cdn-cgi-endpoint/ /fundamentals/reference/cdn-cgi-endpoint/ 301
|
||||
/fundamentals/get-started/task-guides/secure-your-website/ /learning-paths/application-security/ 301
|
||||
/fundamentals/get-started/task-guides/optimize-site-speed/ /learning-paths/optimize-site-speed/ 301
|
||||
/fundamentals/signed-exchanges/ /speed/optimization/other/signed-exchanges/ 301
|
||||
|
|
@ -352,20 +352,108 @@
|
|||
/fundamentals/speed/optimization/ /speed/optimization/ 301
|
||||
/fundamentals/speed/prefetch-urls/ /speed/optimization/content/prefetch-urls/ 301
|
||||
/fundamentals/data-products/analytics-integrations/sumo-logic/ /logs/get-started/enable-destinations/sumo-logic/ 301
|
||||
/support/account-management-billing/account-management/ /fundamentals/account-and-billing/ 301
|
||||
/support/account-management-billing/account-management/adding-multiple-sites-to-cloudflare-via-automation/ /fundamentals/get-started/setup/add-multiple-sites-automation/ 301
|
||||
/support/other-languages/简体中文/通过自动化将多个站点添加到-cloudflare/ /fundamentals/get-started/setup/add-multiple-sites-automation/ 301
|
||||
/support/other-languages/한국어/자동화를-통해-여러-사이트를-cloudflare에-추가/ /fundamentals/get-started/setup/add-multiple-sites-automation/ 301
|
||||
/support/other-languages/deutsch/mehrere-websites-automatisch-in-cloudflare-aufnehmen-/ /fundamentals/get-started/setup/add-multiple-sites-automation/ 301
|
||||
/support/other-languages/español-españa/cómo-añadir-varios-sitios-en-cloudflare-mediante-automatización/ /fundamentals/get-started/setup/add-multiple-sites-automation/ 301
|
||||
/support/other-languages/français-france/ajout-de-plusieurs-sites-à-cloudflare-via-automation/ /fundamentals/get-started/setup/add-multiple-sites-automation/ 301
|
||||
/support/other-languages/日本語/自動化機能を使ってcloudflareに複数のサイトを追加する/ /fundamentals/get-started/setup/add-multiple-sites-automation/ 301
|
||||
/support/other-languages/português-do-brasil/como-adicionar-vários-sites-à-cloudflare-via-automação/ /fundamentals/get-started/setup/add-multiple-sites-automation/ 301
|
||||
/support/firewall/settings/ /fundamentals/security/ 301
|
||||
/support/firewall/settings/understanding-cloudflare-under-attack-mode-advanced-ddos-protection/ /fundamentals/security/under-attack-mode/ 301
|
||||
/support/firewall/settings/understanding-the-cloudflare-browser-integrity-check/ /fundamentals/security/browser-integrity-check/ 301
|
||||
/support/firewall/settings/understanding-the-cloudflare-security-level/ /fundamentals/security/security-level/ 301
|
||||
/support/firewall/settings/using-privacy-pass-with-cloudflare/ /fundamentals/security/privacy-pass/ 301
|
||||
/support/account-management-billing/account-management/ /fundamentals/setup/account-setup/301
|
||||
/support/account-management-billing/account-management/adding-multiple-sites-to-cloudflare-via-automation/ /fundamentals/setup/add-multiple-sites-automation/ 301
|
||||
/support/other-languages/简体中文/通过自动化将多个站点添加到-cloudflare/ /fundamentals/setup/add-multiple-sites-automation/ 301
|
||||
/support/other-languages/한국어/자동화를-통해-여러-사이트를-cloudflare에-추가/ /fundamentals/setup/add-multiple-sites-automation/ 301
|
||||
/support/other-languages/deutsch/mehrere-websites-automatisch-in-cloudflare-aufnehmen-/ /fundamentals/setup/add-multiple-sites-automation/ 301
|
||||
/support/other-languages/español-españa/cómo-añadir-varios-sitios-en-cloudflare-mediante-automatización/ /fundamentals/setup/add-multiple-sites-automation/ 301
|
||||
/support/other-languages/français-france/ajout-de-plusieurs-sites-à-cloudflare-via-automation/ /fundamentals/setup/add-multiple-sites-automation/ 301
|
||||
/support/other-languages/日本語/自動化機能を使ってcloudflareに複数のサイトを追加する/ /fundamentals/setup/add-multiple-sites-automation/ 301
|
||||
/support/other-languages/português-do-brasil/como-adicionar-vários-sites-à-cloudflare-via-automação/ /fundamentals/setup/add-multiple-sites-automation/ 301
|
||||
/support/firewall/settings/ /waf/tools/ 301
|
||||
/support/firewall/settings/understanding-cloudflare-under-attack-mode-advanced-ddos-protection/ /fundamentals/reference/under-attack-mode/ 301
|
||||
/support/firewall/settings/understanding-the-cloudflare-browser-integrity-check/ /waf/tools/browser-integrity-check/ 301
|
||||
/support/firewall/settings/understanding-the-cloudflare-security-level/ /waf/tools/security-level/ 301
|
||||
/support/firewall/settings/using-privacy-pass-with-cloudflare/ /waf/tools/privacy-pass/ 301
|
||||
|
||||
# fundamentals revamp
|
||||
/fundamentals/global-configurations/lists /waf/tools/lists/ 301
|
||||
/fundamentals/global-configurations/lists/link-bulk-redirect-lists/ /rules/url-forwarding/bulk-redirects/concepts/#bulk-redirect-lists 301
|
||||
/fundamentals/global-configurations/lists/ /waf/tools/lists/ 301
|
||||
/fundamentals/global-configurations/ /fundamentals/ 301
|
||||
/fundamentals/customizations/building-custom-dashboards/index/ /fundamentals/api/building-custom-dashboards/ 301
|
||||
/fundamentals/customizations/ /fundamentals/ 301
|
||||
/fundamentals/security/cybersafe/ /fundamentals/reference/policies-compliances/cybersafe/ 301
|
||||
/fundamentals/security/challenge-passage/ /waf/tools/challenge-passage/ 301
|
||||
/fundamentals/glossary/ /fundamentals/reference/glossary/ 301
|
||||
/fundamentals/account-and-billing/login/ /fundamentals/basic-tasks/login/ 301
|
||||
/fundamentals/account-and-billing/account-security/securing-a-compromised-account/ /fundamentals/account-and-billing/account-security/securing-a-compromised-account/ 301
|
||||
/fundamentals/account-and-billing/account-security/zone-holds/ /fundamentals/account-and-billing/account-security/zone-holds/ 301
|
||||
/fundamentals/account-and-billing/account-security/review-audit-logs/ /fundamentals/account-and-billing/account-security/review-audit-logs/ 301
|
||||
/fundamentals/account-and-billing/account-security/manage-active-sessions/ /fundamentals/account-and-billing/account-security/manage-active-sessions/ 301
|
||||
/fundamentals/account-and-billing/account-security/cloudflare-access/ /fundamentals/account-and-billing/account-security/cloudflare-access/ 301
|
||||
/fundamentals/account-and-billing/account-maintenance/delete-account/ /fundamentals/account-and-billing/account-billing/delete-account/ 301
|
||||
/fundamentals/account-and-billing/account-maintenance/updating-billing-info/ /fundamentals/account-and-billing/account-billing/updating-billing-info/ 301
|
||||
/fundamentals/account-and-billing/account-maintenance/understand-invoices/ /fundamentals/account-and-billing/account-billing/understand-invoices/ 301
|
||||
/fundamentals/account-and-billing/account-maintenance/cancel-subscription/ /fundamentals/account-and-billing/account-billing/cancel-subscription/ 301
|
||||
/fundamentals/account-and-billing/account-maintenance/change-plan/ /fundamentals/account-and-billing/account-billing/change-plan/ 301
|
||||
/fundamentals/account-and-billing/account-maintenance/change-super-admin/ /fundamentals/account-and-billing/account-billing/change-super-admin/ 301
|
||||
/fundamentals/account-and-billing/account-maintenance/change-password-or-email/ /fundamentals/account-and-billing/account-billing/change-password-or-email/ 301
|
||||
/fundamentals/account-and-billing/account-maintenance/ /fundamentals/account-and-billing/account-billing/ 301
|
||||
/fundamentals/account-and-billing/members/scope/ /fundamentals/setup/manage-members/scope/ 301
|
||||
/fundamentals/account-and-billing/members/manage/ /fundamentals/setup/manage-members/manage/ 301
|
||||
/fundamentals/account-and-billing/non-contract-products/ /fundamentals/account-and-billing/preview-services/ 301
|
||||
/fundamentals/account-and-billing/account-setup/create-account/ /fundamentals/setup/account-setup/create-account/ 301
|
||||
/fundamentals/account-and-billing/account-setup/verify-email-address/ /fundamentals/setup/account-setup/verify-email-address/ 301
|
||||
/fundamentals/account-and-billing/account-setup/create-billing-profile/ /fundamentals/setup/account-setup/create-billing-profile/ 301
|
||||
/fundamentals/account-and-billing/account-setup/customize-account/language-preference/ /fundamentals/setup/account-setup/customize-account/language-preference/ 301
|
||||
/fundamentals/account-and-billing/account-setup/customize-account/appearance/ /fundamentals/setup/account-setup/customize-account/appearance/ 301
|
||||
/fundamentals/account-and-billing/account-setup/customize-account/account-name/ /fundamentals/setup/account-setup/customize-account/account-name/ 301
|
||||
/fundamentals/account-and-billing/account-setup/customize-account/ /fundamentals/setup/account-setup/customize-account/ 301
|
||||
/fundamentals/account-and-billing/account-setup/customize-account/communication-preference/ /fundamentals/setup/account-setup/customize-account/communication-preference/ 301
|
||||
/fundamentals/data-products/types-of-analytics/ /analytics/types-of-analytics/ 301
|
||||
/fundamentals/data-products/about-analytics/ /analytics/faq/about-analytics/ 301
|
||||
/fundamentals/data-products/analytics-integrations/graylog/index/ /analytics/analytics-integrations/graylog/ 301
|
||||
/fundamentals/data-products/analytics-integrations/looker/index/ /analytics/analytics-integrations/looker/ 301
|
||||
/fundamentals/data-products/analytics-integrations/elastic/index/ /analytics/analytics-integrations/elastic/ 301
|
||||
/fundamentals/data-products/analytics-integrations/splunk/index/ /analytics/analytics-integrations/splunk/ 301
|
||||
/fundamentals/data-products/analytics-integrations/datadog/index/ /analytics/analytics-integrations/datadog/ 301
|
||||
/fundamentals/data-products/analytics-integrations/google-cloud/index/ /analytics/analytics-integrations/google-cloud/ 301
|
||||
/fundamentals/data-products/analytics-integrations/new-relic/index/ /analytics/analytics-integrations/new-relic/ 301
|
||||
/fundamentals/data-products/analytics-integrations/ /analytics/analytics-integrations/ 301
|
||||
/fundamentals/data-products/ /analytics/ 301
|
||||
/fundamentals/get-started/get-started-external-link/ /learning-paths/get-started/ 301
|
||||
/fundamentals/get-started/task-guides/optimize-speed-external-link/ /learning-paths/optimize-site-speed/ 301
|
||||
/fundamentals/get-started/task-guides/prevent-ddos-attacks-external/ /learning-paths/prevent-ddos-attacks/ 301
|
||||
/fundamentals/get-started/task-guides/origin-health/free/ /fundamentals/basic-tasks/protect-your-origin-server/ 301
|
||||
/fundamentals/get-started/task-guides/origin-health/business/ /fundamentals/basic-tasks/protect-your-origin-server/ 301
|
||||
/fundamentals/get-started/task-guides/origin-health/pro/ /fundamentals/basic-tasks/protect-your-origin-server/ 301
|
||||
/fundamentals/get-started/task-guides/origin-health/enterprise/ /fundamentals/basic-tasks/protect-your-origin-server/ 301
|
||||
/fundamentals/get-started/task-guides/origin-health/ /fundamentals/basic-tasks/protect-your-origin-server/ 301
|
||||
/fundamentals/get-started/task-guides/ /fundamentals/basic-tasks/ 301
|
||||
/fundamentals/get-started/setup/ /fundamentals/setup/ 301
|
||||
/fundamentals/get-started/setup/minimize-downtime/ /fundamentals/basic-tasks/minimize-downtime/ 301
|
||||
/fundamentals/get-started/concepts/what-is-cloudflare/ /fundamentals/concepts/what-is-cloudflare/ 301
|
||||
/fundamentals/get-started/concepts/cloudflare-challenges/ /firewall/cf-firewall-rules/cloudflare-challenges/ 301
|
||||
/fundamentals/get-started/concepts/accounts-and-zones/ /fundamentals/concepts/accounts-and-zones/ 301
|
||||
/fundamentals/get-started/concepts/cloudflare-ip-addresses/ /fundamentals/concepts/cloudflare-ip-addresses/ 301
|
||||
/fundamentals/get-started/concepts/network-layers/ /fundamentals/concepts/network-layers/ 301
|
||||
/fundamentals/get-started/concepts/ /fundamentals/concepts/ 301
|
||||
/fundamentals/get-started/basic-tasks/find-account-and-zone-ids/ /fundamentals/setup/find-account-and-zone-ids/ 301
|
||||
/fundamentals/get-started/basic-tasks/maintenance-mode/ /fundamentals/basic-tasks/maintenance-mode/ 301
|
||||
/fundamentals/get-started/basic-tasks/access-cloudflare-resources/ /fundamentals/ 301
|
||||
/fundamentals/get-started/basic-tasks/manage-domains/remove-domain/ /fundamentals/setup/manage-domains/remove-domain/ 301
|
||||
/fundamentals/get-started/basic-tasks/manage-domains/pause-cloudflare/ /fundamentals/setup/manage-domains/pause-cloudflare/ 301
|
||||
/fundamentals/get-started/basic-tasks/manage-domains/move-domain/ /fundamentals/setup/manage-domains/move-domain/ 301
|
||||
/fundamentals/get-started/basic-tasks/manage-domains/ /fundamentals/setup/manage-domains/ 301
|
||||
/fundamentals/get-started/basic-tasks/manage-domains/redirect-domain/ /fundamentals/setup/manage-domains/redirect-domain/ 301
|
||||
/fundamentals/get-started/basic-tasks/cloudflare-without-changing-nameservers/ /fundamentals/setup/use-cloudflare-without-changing-nameservers/ 301
|
||||
/fundamentals/get-started/basic-tasks/interact-with-cloudflare/ /fundamentals/basic-tasks/interact-with-cloudflare/ 301
|
||||
/fundamentals/get-started/basic-tasks/manage-subdomains/ /fundamentals/basic-tasks/manage-subdomains/ 301
|
||||
/fundamentals/get-started/basic-tasks/report-abuse/provide-specific-urls/ /fundamentals/reference/report-abuse/provide-specific-urls/ 301
|
||||
/fundamentals/get-started/basic-tasks/report-abuse/complaint-types/ /fundamentals/reference/report-abuse/complaint-types/ 301
|
||||
/fundamentals/get-started/basic-tasks/report-abuse/ /fundamentals/reference/report-abuse/ 301
|
||||
/fundamentals/get-started/basic-tasks/access-compliance-docs/ /fundamentals/reference/policies-compliances/compliance-docs/ 301
|
||||
/fundamentals/get-started/basic-tasks/under-ddos-attack/ /fundamentals/basic-tasks/under-ddos-attack/ 301
|
||||
/fundamentals/get-started/basic-tasks/test-speed/ /fundamentals/basic-tasks/test-speed/ 301
|
||||
/fundamentals/get-started/basic-tasks/ /fundamentals/basic-tasks/ 301
|
||||
/fundamentals/get-started/reference/cloudflare-site-crawling/ /fundamentals/reference/cloudflare-site-crawling/ 301
|
||||
/fundamentals/get-started/reference/content-security-policies/ /fundamentals/reference/policies-compliances/content-security-policies/ 301
|
||||
/fundamentals/get-started/reference/cloudflare-ray-id/ /fundamentals/reference/cloudflare-ray-id/ 301
|
||||
/fundamentals/get-started/reference/ /fundamentals/reference/ 301
|
||||
/fundamentals/get-started/ /fundamentals/setup/ 301
|
||||
|
||||
|
||||
# gateway
|
||||
/gateway/about/ /cloudflare-one/policies/gateway/ 301
|
||||
|
|
@ -405,7 +493,7 @@
|
|||
/support/troubleshooting/general-troubleshooting/troubleshoot-image-resizing-problems/ /images/image-resizing/troubleshooting/ 301
|
||||
|
||||
# learning-paths
|
||||
/learning-paths/technology-partner-integrations/ /fundamentals/partners/ 301
|
||||
/learning-paths/technology-partner-integrations/ /fundamentals/reference/partners/ 301
|
||||
/support/about-cloudflare/attack-preparation-and-response/best-practices-ddos-preventative-measures/ /learning-paths/prevent-ddos-attacks/ 301
|
||||
# more redirects in the /dynamic/ section
|
||||
|
||||
|
|
@ -522,11 +610,11 @@
|
|||
/pages/tutorials/build-an-api-with-workers/ /pages/tutorials/build-an-api-with-pages-functions/ 301
|
||||
|
||||
# partners
|
||||
/partners/ /fundamentals/partners/ 301
|
||||
/partners/analytics/ /fundamentals/partners/#analytics-integrations 301
|
||||
/partners/logs/ /fundamentals/partners/#cloudflare-logs 301
|
||||
/partners/ /fundamentals/reference/partners/ 301
|
||||
/partners/analytics/ /fundamentals/reference/partners/#analytics-integrations 301
|
||||
/partners/logs/ /fundamentals/reference/partners/#cloudflare-logs 301
|
||||
/partners/email-security/ /email-security/partners/ 301
|
||||
/partners/network-interconnect/ /fundamentals/partners/#cloudflare-network-interconnect 301
|
||||
/partners/network-interconnect/ /fundamentals/reference/partners/#cloudflare-network-interconnect 301
|
||||
/partners/tenant/ /tenant/ 301
|
||||
|
||||
# page-shield
|
||||
|
|
@ -766,7 +854,6 @@
|
|||
/waf/ddos-l34-mitigation/configure-api/ /ddos-protection/managed-rulesets/network/configure-api/ 301
|
||||
/waf/ddos-l7-mitigation/ /ddos-protection/managed-rulesets/http/ 301
|
||||
/waf/ddos-l7-mitigation/configure-dashboard/ /ddos-protection/managed-rulesets/http/configure-dashboard/ 301
|
||||
/waf/firewall-rules/ /waf/custom-rules/ 301
|
||||
/waf/managed-rulesets/cloudflare-managed-ruleset/ /waf/managed-rules/reference/cloudflare-managed-ruleset/ 301
|
||||
/waf/managed-rulesets/owasp-core-ruleset/ /waf/managed-rules/reference/owasp-core-ruleset/ 301
|
||||
/waf/managed-rulesets/exposed-credentials-check/ /waf/managed-rules/reference/exposed-credentials-check/ 301
|
||||
|
|
@ -865,6 +952,7 @@
|
|||
/workers/reference/apis/response/ /workers/runtime-apis/response/ 301
|
||||
/workers/reference/apis/streams/ /workers/runtime-apis/streams/ 301
|
||||
/workers/learning/using-streams/ /workers/runtime-apis/streams/ 301
|
||||
/workers/runtime-apis/streams/use-streams/ /workers/runtime-apis/streams/ 301
|
||||
/workers/reference/apis/web-crypto/ /workers/runtime-apis/web-crypto/ 301
|
||||
/workers/reference/cache-api/ /workers/runtime-apis/cache/ 301
|
||||
/workers/reference/cloudflare-features/ /workers/runtime-apis/request/ 301
|
||||
|
|
@ -948,9 +1036,6 @@
|
|||
/workers/get-started/storage-options/ /workers/learning/storage-options 301
|
||||
/workers/tutorials/deploy-a-static-wordpress-site/ /pages/how-to/deploy-a-wordpress-site/ 301
|
||||
/workers/wrangler/get-started/ /workers/wrangler/install-and-update/ 301
|
||||
/workers/wrangler/workers-kv/ /kv/ 301
|
||||
/workers/runtime-apis/kv/ /kv/api/ 301
|
||||
/workers/learning/how-kv-works/ /kv/learning/how-kv-works/ 301
|
||||
/workers/platform/storage-objects/ /workers/platform/storage-options/ 301
|
||||
/workers/wrangler-legacy/migration/deprecations/ /workers/wrangler/deprecations/ 301
|
||||
/workers/wrangler-legacy/migration/eject-webpack/ /workers/wrangler/migration/v1-to-v2/eject-webpack/ 301
|
||||
|
|
@ -1198,10 +1283,10 @@ workers/runtime-apis/fetch-event/#passthroughonexception /workers/runtime-apis/h
|
|||
/cloudflare-one/policies/data-loss-prevention/configuration-guides/* /cloudflare-one/policies/data-loss-prevention/dlp-policies/common-policies/ 301
|
||||
/distributed-web/* /web3/:splat 301
|
||||
/docs-engine/* https://github.com/cloudflare/cloudflare-docs/blob/production/README.md 301
|
||||
/fundamentals/internet/* /fundamentals/the-internet/ 301
|
||||
/fundamentals/internet/* /fundamentals/reference/the-internet/ 301
|
||||
/internet/* https://www.cloudflare.com/learning/ 301
|
||||
/fundamentals/get-started/basic-tasks/account-maintenance/* /fundamentals/account-and-billing/account-maintenance/:splat 301
|
||||
/fundamentals/get-started/setup/troubleshooting/* /fundamentals/get-started/setup/add-site/ 301
|
||||
/fundamentals/get-started/setup/troubleshooting/* /fundamentals/setup/account-setup/add-site/ 301
|
||||
/fundamentals/get-started/basic-tasks/account-security/* /fundamentals/account-and-billing/account-security/:splat 301
|
||||
/fundamentals/get-started/origin-health/* /fundamentals/get-started/task-guides/origin-health/:splat 301
|
||||
/fundamentals/get-started/setup/account-setup/* /fundamentals/account-and-billing/account-setup/:splat 301
|
||||
|
|
@ -1272,4 +1357,4 @@ workers/runtime-apis/fetch-event/#passthroughonexception /workers/runtime-apis/h
|
|||
|
||||
/ssl/custom-certificates/* /ssl/edge-certificates/custom-certificates/:splat 301
|
||||
/logs/analytics-integrations/* /fundamentals/data-products/analytics-integrations/:splat 301
|
||||
/fundamentals/notifications/* /notifications/:splat 301
|
||||
/fundamentals/notifications/* /notifications/:splat 301
|
||||
|
|
@ -10,7 +10,7 @@ weight: 2
|
|||
Cloudflare account analytics lets you access a wide range of aggregated metrics from all the sites under a specific Cloudflare account.
|
||||
|
||||
{{<Aside type="note">}}
|
||||
For general information about all of Cloudflare's analytics offerings, refer to [About Cloudflare Analytics](/fundamentals/data-products/about-analytics/).
|
||||
For general information about all of Cloudflare's analytics offerings, refer to [About Cloudflare Analytics](/analytics/faq/about-analytics/).
|
||||
{{</Aside>}}
|
||||
|
||||
___
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ ___
|
|||
## Edge Network errors
|
||||
|
||||
- `400` - Bad Request intercepted at the Cloudflare Edge (for example, missing or bad HTTP header)
|
||||
- `403` - Security functionality (for example, Web Application Firewall, Browser Integrity Check, [Cloudflare challenges](/fundamentals/get-started/concepts/cloudflare-challenges/), and most 1xxx error codes)
|
||||
- `403` - Security functionality (for example, Web Application Firewall, Browser Integrity Check, [Cloudflare challenges](/firewall/cf-firewall-rules/cloudflare-challenges/), and most 1xxx error codes)
|
||||
- `409` - DNS errors typically in the form of 1000 or 1001 error code
|
||||
- `413` - File size upload exceeded the maximum size allowed (configured under the Speed app)
|
||||
- `444` - Used by Nginx to indicate that the server has returned no information to the client, and closed the connection. This error code is internal to Nginx and is **not** returned to the client.
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ Cloudflare classifies the threats that it blocks or challenges. To help you unde
|
|||
|
||||
The source of the request was not legitimate or the request itself was malicious. Users would receive a [1010 error page](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors/#error-1010-the-owner-of-this-website-has-banned-your-access-based-on-your-browsers-signature) in their browser.
|
||||
|
||||
Cloudflare's [Browser Integrity Check](/fundamentals/security/browser-integrity-check/) looks for common HTTP headers abused most commonly by spammers and denies them access to your page. It will also challenge visitors that do not have a user agent or a non standard user agent (also commonly used by bots, crawlers, or visitors).
|
||||
Cloudflare's [Browser Integrity Check](/waf/tools/browser-integrity-check/) looks for common HTTP headers abused most commonly by spammers and denies them access to your page. It will also challenge visitors that do not have a user agent or a non standard user agent (also commonly used by bots, crawlers, or visitors).
|
||||
|
||||
## Blocked hotlink
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ title: Total threats stopped
|
|||
Total Threats Stopped measures the number of “suspicious” and “bad” requests that were aimed at your site. Requests receive these labels by our IP Reputation Database as they enter Cloudflare’s network:
|
||||
|
||||
- **Legitimate:** request pass directly to your site
|
||||
- **Suspicious:** request has been challenged with a [Cloudflare challenge](/fundamentals/get-started/concepts/cloudflare-challenges/)
|
||||
- **Suspicious:** request has been challenged with a [Cloudflare challenge](/firewall/cf-firewall-rules/cloudflare-challenges/)
|
||||
- **Bad:** request has been blocked because our Browser Integrity Check, or because of user configured settings like WAF rules or IP range block.
|
||||
|
||||
Cloudflare uses Threat Scores gathered from sources such as Project Honeypot, as well as our own communities' traffic to determine whether a visitor is legitimate or malicious. When a legitimate visitor passes a challenge, that helps offset the Threat Score against the previous negative behavior seen from that IP address. Our system learns who is a threat from this activity.
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ weight: 1
|
|||
The Cloudflare zone analytics is a major component of the overall Cloudflare Analytics product line. Specifically, this app gives you access to a wide range of metrics, collected at the website or domain level.
|
||||
|
||||
{{<Aside type="note">}}
|
||||
Read [Cloudflare Analytics](/fundamentals/data-products/about-analytics/)
|
||||
Read [Cloudflare Analytics](/analytics/faq/about-analytics/)
|
||||
for general information about all of Cloudflare's analytics offerings.
|
||||
You can also understand the characteristics of the data that Cloudflare
|
||||
captures and processes.
|
||||
|
|
|
|||
|
|
@ -2,8 +2,6 @@
|
|||
pcx_content_type: navigation
|
||||
title: Analytics integrations
|
||||
weight: 7
|
||||
aliases:
|
||||
- /fundamentals/data-products/analytics-integrations/
|
||||
---
|
||||
|
||||
# Analytics integrations
|
||||
|
|
|
|||
|
|
@ -3,8 +3,6 @@ pcx_content_type: how-to
|
|||
title: Datadog
|
||||
weight: 98
|
||||
layout: single
|
||||
aliases:
|
||||
- /fundamentals/data-products/analytics-integrations/datadog/
|
||||
---
|
||||
|
||||
# Datadog
|
||||
|
|
@ -37,7 +35,7 @@ To install the Cloudflare App for Datadog:
|
|||
|
||||
- **Account name**: (Optional) This can be any value. It has not impact on the site data pulled from Cloudflare.
|
||||
|
||||
- **Email**: This value helps keep your account safe. We recommend creating a dedicated Cloudflare user for analytics with the [_Analytics_ role](/fundamentals/account-and-billing/members/roles/) (read-only). Note that the _Analytics_ role is available to Enterprise customers only.
|
||||
- **Email**: This value helps keep your account safe. We recommend creating a dedicated Cloudflare user for analytics with the [_Analytics_ role](/fundamentals/setup/manage-members/roles/) (read-only). Note that the _Analytics_ role is available to Enterprise customers only.
|
||||
|
||||
- **API Key**: Enter your Cloudflare Global API key. For details refer to [API Keys](/fundamentals/api/get-started/keys/).
|
||||
|
||||
|
|
|
|||
|
|
@ -3,8 +3,6 @@ pcx_content_type: how-to
|
|||
title: Elastic
|
||||
weight: 100
|
||||
layout: single
|
||||
aliases:
|
||||
- /fundamentals/data-products/analytics-integrations/elastic/
|
||||
---
|
||||
|
||||
# Elastic
|
||||
|
|
|
|||
|
|
@ -3,8 +3,6 @@ pcx_content_type: how-to
|
|||
title: Google Cloud
|
||||
weight: 101
|
||||
layout: single
|
||||
aliases:
|
||||
- /fundamentals/data-products/analytics-integrations/google-cloud/
|
||||
---
|
||||
|
||||
# Google Cloud
|
||||
|
|
|
|||
|
|
@ -3,8 +3,6 @@ pcx_content_type: how-to
|
|||
title: Graylog
|
||||
weight: 102
|
||||
layout: single
|
||||
aliases:
|
||||
- /fundamentals/data-products/analytics-integrations/graylog/
|
||||
---
|
||||
|
||||
# Graylog
|
||||
|
|
|
|||
|
|
@ -3,8 +3,6 @@ pcx_content_type: how-to
|
|||
title: Looker
|
||||
weight: 102
|
||||
layout: single
|
||||
aliases:
|
||||
- /fundamentals/data-products/analytics-integrations/looker/
|
||||
---
|
||||
|
||||
# Looker
|
||||
|
|
@ -15,7 +13,7 @@ This tutorial explains how to analyze [Cloudflare Logs](https://www.cloudflare.c
|
|||
|
||||
If you have not used Cloudflare Logs before, refer to the [Logs documentation](/logs/) for more details. Contact your Cloudflare Customer Account Team to enable logs for your account.
|
||||
|
||||
This tutorial uses Cloudflare Logpush to send logs to [Google Cloud Storage Bucket and Cloud Function](/fundamentals/data-products/analytics-integrations/google-cloud/) and then import them into Google Big Query.
|
||||
This tutorial uses Cloudflare Logpush to send logs to [Google Cloud Storage Bucket and Cloud Function](/analytics/analytics-integrations/google-cloud/) and then import them into Google Big Query.
|
||||
|
||||
### Prerequisites
|
||||
|
||||
|
|
|
|||
|
|
@ -3,8 +3,6 @@ pcx_content_type: how-to
|
|||
title: New Relic
|
||||
weight: 103
|
||||
layout: single
|
||||
aliases:
|
||||
- /fundamentals/data-products/analytics-integrations/new-relic/
|
||||
---
|
||||
|
||||
# New Relic
|
||||
|
|
|
|||
|
|
@ -3,9 +3,6 @@ pcx_content_type: how-to
|
|||
title: Splunk
|
||||
weight: 104
|
||||
layout: single
|
||||
aliases:
|
||||
- /fundamentals/data-products/analytics-integrations/splunk/
|
||||
|
||||
---
|
||||
|
||||
# Splunk
|
||||
|
|
|
|||
|
|
@ -4,8 +4,6 @@ title: About Cloudflare Analytics
|
|||
weight: 1
|
||||
meta:
|
||||
title: A quick overview of Cloudflare Analytics
|
||||
aliases:
|
||||
- /fundamentals/data-products/about-analytics/
|
||||
---
|
||||
|
||||
# About Cloudflare Analytics
|
||||
|
|
@ -14,7 +12,7 @@ In an effort to make analytics an ubiquitous component of all Cloudflare's produ
|
|||
|
||||
You can access root-level analytics that give you an overview of metadata related to your Cloudflare account, analytics related to specific properties and products, and the GraphQL API that gives you more control over how you visualize the analytics and log information available on the Cloudflare dashboard.
|
||||
|
||||
Refer to [Types of analytics](/fundamentals/data-products/types-of-analytics/) for more information regarding this subject.
|
||||
Refer to [Types of analytics](/analytics/types-of-analytics/) for more information regarding this subject.
|
||||
|
||||
## How Cloudflare captures and processes analytics data
|
||||
|
||||
|
|
@ -22,7 +20,7 @@ The underlying datasets that Cloudflare Analytics captures and processes share t
|
|||
|
||||
* All metrics reflect traffic proxied through the Cloudflare network (also known as orange-clouded), as configured via DNS records in the Cloudflare DNS app. Note that for a [CNAME setup](/dns/zone-setups/partial-setup/), Cloudflare is unable to offer DNS metrics.
|
||||
* Cloudflare does not count traffic for unproxied DNS records. However, if your site is not proxied through Cloudflare but Cloudflare is your authoritative DNS server, then we are able to collect DNS metrics.
|
||||
* Cloudflare can only proxy information for traffic targeting [specific ports](/fundamentals/get-started/reference/network-ports/).
|
||||
* Cloudflare can only proxy information for traffic targeting [specific ports](/fundamentals/reference/network-ports/).
|
||||
* In determining the originating country, Cloudflare uses the IP address associated with each request. Learn about [Configuring Cloudflare IP Geolocation](https://support.cloudflare.com/hc/articles/200168236).
|
||||
|
||||
## Apparent data discrepancies
|
||||
|
|
|
|||
|
|
@ -276,7 +276,7 @@ Here are some helpful articles about working with the Cloudflare Analytics API a
|
|||
[1]: </analytics/graphql-api/features/discovery/introspection/>
|
||||
[2]: </analytics/graphql-api/getting-started/compose-graphql-query/>
|
||||
[3]: </analytics/graphql-api/getting-started/execute-graphql-query/>
|
||||
[5]: </fundamentals/get-started/basic-tasks/find-account-and-zone-ids/>
|
||||
[5]: </fundamentals/setup/find-account-and-zone-ids/>
|
||||
[6]: <https://www.howtographql.com/>
|
||||
[7]: <https://graphql.org/learn/thinking-in-graphs/>
|
||||
[8]: <https://graphql.org/learn/schema/>
|
||||
|
|
|
|||
|
|
@ -259,7 +259,7 @@ Network Analytics currently has these limitations:
|
|||
- Application layer rules
|
||||
- Gatekeeper and manually applied rules
|
||||
- [flowtrackd](https://blog.cloudflare.com/announcing-flowtrackd/) (Advanced TCP protection) (available in Network Analytics v2)
|
||||
- WARP traffic and [Orange-clouded traffic](/fundamentals/get-started/concepts/how-cloudflare-works/)
|
||||
- WARP traffic and [Orange-clouded traffic](/fundamentals/concepts/how-cloudflare-works/)
|
||||
|
||||
- Data from Cloudflare services that proxy traffic, such as CDN, is not available in Network Analytics.
|
||||
|
||||
|
|
|
|||
|
|
@ -2,8 +2,6 @@
|
|||
pcx_content_type: reference
|
||||
title: Types of analytics
|
||||
weight: 2
|
||||
aliases:
|
||||
- /fundamentals/data-products/types-of-analytics/
|
||||
---
|
||||
|
||||
# Types of analytics
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ To enable [Argo Smart Routing](https://dash.cloudflare.com/?to=/:account/:zone/t
|
|||
3. For **Argo Smart Routing**, switch the toggle to **On**.
|
||||
4. Provide your billing information.
|
||||
|
||||
* If you do not have a [billing profile](/fundamentals/account-and-billing/account-setup/create-billing-profile/), enter your billing information.
|
||||
* If you do not have a [billing profile](/fundamentals/setup/account-setup/create-billing-profile/), enter your billing information.
|
||||
|
||||
* If you have a billing profile, confirm your billing information.
|
||||
|
||||
|
|
@ -29,7 +29,7 @@ To enable [Argo Smart Routing](https://dash.cloudflare.com/?to=/:account/:zone/t
|
|||
|
||||
To enable or disable Argo Smart Routing with the API, send a [`PATCH`](/api/operations/argo-smart-routing-patch-argo-smart-routing-setting) request with the `value` parameter set to your desired setting (`"on"` or `"off"`).
|
||||
|
||||
You will need to already have a [billing profile](/fundamentals/account-and-billing/account-setup/create-billing-profile/) on your account to enable Argo Smart Routing.
|
||||
You will need to already have a [billing profile](/fundamentals/setup/account-setup/create-billing-profile/) on your account to enable Argo Smart Routing.
|
||||
|
||||
{{</tab>}}
|
||||
{{</tabs>}}
|
||||
|
|
|
|||
|
|
@ -9,4 +9,4 @@ Cloudflare uses the `__cf_bm cookie` to smooth out the Bot Score and reduce fals
|
|||
|
||||
The Bot Management cookie measures a single user's request pattern and applies it to the machine learning data to generate a reliable Bot Score for all of that user's requests.
|
||||
|
||||
For more details, refer to [Cloudflare Cookies](/fundamentals/get-started/reference/cloudflare-cookies/).
|
||||
For more details, refer to [Cloudflare Cookies](/fundamentals/reference/policies-compliances/cloudflare-cookies/).
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ weight: 0
|
|||
WordPress relies on making loopback requests to monitor and occasionally administer its websites. Customers can opt-in to optimize Super Bot Fight Mode for WordPress. If this feature is enabled, automated loopback requests made by your WordPress site will be authorized even when Super Bot Fight Mode blocks other bots.
|
||||
|
||||
{{<Aside type="note">}}
|
||||
Loopback requests may also be blocked by [I’m Under Attack mode](/fundamentals/security/under-attack-mode/) or certain [WAF custom rules](/waf/custom-rules/).
|
||||
Loopback requests may also be blocked by [I’m Under Attack mode](/fundamentals/reference/under-attack-mode/) or certain [WAF custom rules](/waf/custom-rules/).
|
||||
{{</Aside>}}
|
||||
|
||||
## Enable Optimize for WordPress
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ meta:
|
|||
|
||||
To prevent issues and simplify the advertisement process during an attack scenario, complete the following tasks.
|
||||
|
||||
- **Assign appropriate user roles.** Ensure that users assigned to manage the status of IP prefix advertisement have the **Administrator** or **Super Administrator** role in your Cloudflare account. For more information, refer to [Setting up Multi-user accounts on Cloudflare](/fundamentals/account-and-billing/members/).
|
||||
- **Assign appropriate user roles.** Ensure that users assigned to manage the status of IP prefix advertisement have the **Administrator** or **Super Administrator** role in your Cloudflare account. For more information, refer to [Setting up Multi-user accounts on Cloudflare](/fundamentals/setup/manage-members/).
|
||||
|
||||
- **Get a list of the Prefix IDs you want to manage.** Maintain a list of Cloudflare prefix IDs to simplify dynamic advertisement management and operations. To obtain Prefix IDs, review [obtain prefix IDs](/byoip/how-to/configure-dynamic-advertisement/#obtain-prefix-ids) from the dashboard or use the [list prefixes](/api/operations/ip-address-management-prefixes-list-prefixes) operation in the Cloudflare API. Refer to these Prefix IDs when managing prefix advertisement.
|
||||
|
||||
|
|
|
|||
|
|
@ -32,6 +32,6 @@ Contact your sales team for more information on these steps.
|
|||
|
||||
## Step 3 — Onboard your domains to the Cloudflare China Network
|
||||
|
||||
After content vetting is complete, [add your domains to Cloudflare](/fundamentals/get-started/setup/add-site/).
|
||||
After content vetting is complete, [add your domains to Cloudflare](/fundamentals/setup/account-setup/add-site/).
|
||||
|
||||
It will take a minimum of 24 hours to enable user traffic (that is, until DNS starts answering with JD Cloud's network IP addresses).
|
||||
|
|
@ -10,7 +10,7 @@ inputParameters: planReqs
|
|||
|
||||
Before you start creating custom hostnames:
|
||||
|
||||
1. [Add](/fundamentals/get-started/setup/add-site/) your zone to Cloudflare $1
|
||||
1. [Add](/fundamentals/setup/account-setup/add-site/) your zone to Cloudflare $1
|
||||
2. [Enable](/cloudflare-for-platforms/cloudflare-for-saas/start/enable/) Cloudflare for SaaS for your zone.
|
||||
3. (optional) Review the following documentation:
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ Use custom hostname analytics to help your organization with billing and infrast
|
|||
|
||||
If you see one customer is using more data than another, you might increase their bill. If requests are increasing in a certain geographic region, you might want to increase the origin servers in that region.
|
||||
|
||||
To access custom hostname analytics, either [use the dashboard](/fundamentals/data-products/about-analytics/) and filter by the `Host` field or [use the GraphQL API](/analytics/graphql-api/) and filter by the `clientRequestHTTPHost` field. For more details, refer to our tutorial on [Querying HTTP events by hostname with GraphQL](/analytics/graphql-api/tutorials/end-customer-analytics/).
|
||||
To access custom hostname analytics, either [use the dashboard](/analytics/faq/about-analytics/) and filter by the `Host` field or [use the GraphQL API](/analytics/graphql-api/) and filter by the `clientRequestHTTPHost` field. For more details, refer to our tutorial on [Querying HTTP events by hostname with GraphQL](/analytics/graphql-api/tutorials/end-customer-analytics/).
|
||||
|
||||
## Share Cloudflare data with your customers
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ Before you can employ Early Hints for SaaS, you need to create a custom hostname
|
|||
|
||||
## Enable Early Hints per custom hostname via the API
|
||||
|
||||
1. [Locate your zone ID](/fundamentals/get-started/basic-tasks/find-account-and-zone-ids/), available in the Cloudflare dashboard.
|
||||
1. [Locate your zone ID](/fundamentals/setup/find-account-and-zone-ids/), available in the Cloudflare dashboard.
|
||||
|
||||
2. Locate your Authentication Key by selecting **My Profile** > **API tokens** > **Global API Key**.
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ This is not an exhaustive list of Cloudflare products and features.
|
|||
| [API Shield](/api-shield/) | Yes | No |
|
||||
| [Argo Smart Routing](/argo-smart-routing/) | No | Yes | Customer zones can still use Smart Routing for non-O2O traffic. |
|
||||
| [Bot Management](/bots/plans/bm-subscription/) | Yes* | Yes* | Bot Management cannot be enabled on both the customer zone and the SaaS zone |
|
||||
| [Browser Integrity Check](/fundamentals/security/browser-integrity-check/) | Yes | Yes |
|
||||
| [Browser Integrity Check](/waf/tools/browser-integrity-check/) | Yes | Yes |
|
||||
| [Cache](/cache/) | Yes* | Yes | Though caching is possible on a customer zone, it is generally discouraged (especially for HTML).<br/><br/>Your SaaS provider likely performs its own caching outside of Cloudflare and caching on your zone might lead to out-of-sync or stale cache states.<br/><br/>Customer zones can still cache content that are not routed through a SaaS provider's zone.|
|
||||
| [China Network](/china-network/) | No | No |
|
||||
| [DNS](/dns/) | Yes* | Yes | As a SaaS customer, do not remove the records related to your Cloudflare for SaaS setup.<br/><br/>Otherwise, your traffic will begin routing away from your SaaS provider. |
|
||||
|
|
@ -41,7 +41,7 @@ This is not an exhaustive list of Cloudflare products and features.
|
|||
| [Origin Rules](/rules/origin-rules/) | No | Yes | Origin Rules that match the subdomain used for O2O may block or interfere with the flow of visitors to your website. |
|
||||
| [Polish](/images/polish/) | Yes* | Yes | Polish only runs on cached assets. If the customer zone is bypassing cache for SaaS zone destined traffic, then images optimized by Polish will not be loaded from origin. |
|
||||
| [Rate Limiting](/waf/rate-limiting-rules/) | Yes* | Yes | Rate Limiting rules that match the subdomain used for O2O may block or interfere with the flow of visitors to your website. |
|
||||
| [Security Level](/fundamentals/security/security-level/) | Yes | Yes |
|
||||
| [Security Level](/waf/tools/security-level/) | Yes | Yes |
|
||||
| [Spectrum](/spectrum/) | No | No |
|
||||
| [Transform Rules](/rules/transform/) | Yes* | Yes | Transform Rules that match the subdomain used for O2O may block or interfere with the flow of visitors to your website. |
|
||||
| [WAF custom rules](/waf/custom-rules/) | Yes | Yes | WAF custom rules that match the subdomain used for O2O may block or interfere with the flow of visitors to your website. |
|
||||
|
|
|
|||
|
|
@ -48,4 +48,4 @@ If desired, you could also manually fetch the DCV tokens and share them with you
|
|||
|
||||
## Moved domains
|
||||
|
||||
If you [move your SaaS zone to another account](/fundamentals/get-started/basic-tasks/manage-domains/move-domain/), you will need to update the `CNAME` record with a new hostname value.
|
||||
If you [move your SaaS zone to another account](/fundamentals/setup/manage-domains/move-domain/), you will need to update the `CNAME` record with a new hostname value.
|
||||
|
|
@ -30,7 +30,7 @@ curl -X POST "https://api.cloudflare.com/client/v4/zones/{zone:id}/custom_hostna
|
|||
|
||||
To apply WAF to your custom hostname, you need to create an association between your customer’s domain and the WAF configuration that you’d like to attach to it. Cloudflare’s product, [custom metadata](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/custom-metadata/) allows you to do this via the API.
|
||||
|
||||
1. [Locate your zone ID](/fundamentals/get-started/basic-tasks/find-account-and-zone-ids/), available in the Cloudflare dashboard.
|
||||
1. [Locate your zone ID](/fundamentals/setup/find-account-and-zone-ids/), available in the Cloudflare dashboard.
|
||||
|
||||
2. Locate your Authentication Key by selecting **My Profile** > **API tokens** > **Global API Key**.
|
||||
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ To enable Cloudflare for SaaS for your account:
|
|||
3. Go to **SSL/TLS** > **Custom Hostnames**.
|
||||
4. Select **Enable**.
|
||||
5. The next step depends on the zone's plan:
|
||||
- **Enterprise**: Can preview this product as a [non-contract service](/fundamentals/account-and-billing/non-contract-products/), which provide full access, free of metered usage fees, limits, and certain other restrictions.
|
||||
- **Enterprise**: Can preview this product as a [non-contract service](/fundamentals/account-and-billing/preview-services/), which provide full access, free of metered usage fees, limits, and certain other restrictions.
|
||||
- **Non-enterprise**: Will have to enter payment information.
|
||||
|
||||
{{<Aside type="note">}}
|
||||
|
|
|
|||
|
|
@ -73,7 +73,7 @@ Block specific IP addresses that are known to be malicious or pose a threat to y
|
|||
|
||||
## CIPA Filter
|
||||
|
||||
The CIPA Filter is a collection of subcategories that encompass a wide range of topics that could be harmful or inappropriate for minors. It is used as a part of [Project Cybersafe Schools](/fundamentals/security/cybersafe/) to block access to unwanted or harmful online content.
|
||||
The CIPA Filter is a collection of subcategories that encompass a wide range of topics that could be harmful or inappropriate for minors. It is used as a part of [Project Cybersafe Schools](/fundamentals/reference/policies-compliances/cybersafe/) to block access to unwanted or harmful online content.
|
||||
|
||||
|
||||
| Selector | Operator | Value | Action |
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ By adding a Dashboard SSO application to your Cloudflare Zero Trust account, you
|
|||
|
||||
## Prerequisites
|
||||
|
||||
All users in your email domain must exist as a member in your Cloudflare account and IdP. To add users to your Cloudflare account, refer to [Manage Cloudflare account access](/fundamentals/account-and-billing/members/).
|
||||
All users in your email domain must exist as a member in your Cloudflare account and IdP. To add users to your Cloudflare account, refer to [Manage Cloudflare account access](/fundamentals/setup/manage-members/).
|
||||
|
||||
{{<Aside>}}
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ Cloudflare Access allows you to securely publish internal tools and applications
|
|||
|
||||
## Prerequisites
|
||||
|
||||
- [Add your domain](/fundamentals/get-started/setup/add-site/) to Cloudflare.
|
||||
- [Add your domain](/fundamentals/setup/account-setup/add-site/) to Cloudflare.
|
||||
- [Change your domain nameservers](/dns/zone-setups/full-setup/) to Cloudflare, or configure a [partial (`CNAME`) setup](/dns/zone-setups/partial-setup/).
|
||||
|
||||
## 1. Add your application to Access
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ weight: 21
|
|||
|
||||
When creating a Cloudflare Zero Trust account, you will be given the Super Administrator role. As a Super Administrator, you can invite members to join your Zero Trust account and assign them different roles. There is no limit to the number of members which can be added to a given account. Any members with the proper permissions will be able to make configuration changes while actively logged into Zero Trust (unless [read-only mode](/cloudflare-one/api-terraform/#set-dashboard-to-read-only) is enabled).
|
||||
|
||||
To check the list of members in your account, or to manage roles and permissions, refer to our [Account setup](/fundamentals/account-and-billing/members/) documentation.
|
||||
To check the list of members in your account, or to manage roles and permissions, refer to our [Account setup](/fundamentals/setup/manage-members/) documentation.
|
||||
|
||||
## Zero Trust roles
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ Device Information Only mode allows you to enforce device posture rules when a u
|
|||
|
||||
To set up Device Information Only mode:
|
||||
|
||||
1. Enable client certificate provisioning for [your zone](/fundamentals/get-started/basic-tasks/find-account-and-zone-ids/):
|
||||
1. Enable client certificate provisioning for [your zone](/fundamentals/setup/find-account-and-zone-ids/):
|
||||
|
||||
```sh
|
||||
curl -X PATCH 'https://api.cloudflare.com/client/v4/zones/<ZONE ID>/devices/policy/certificates' \
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ To complete the steps in this guide, you will need:
|
|||
|
||||
- [A Google Cloud Project](https://cloud.google.com/resource-manager/docs/creating-managing-projects#creating_a_project) and [GCP CLI installed and authenticated](https://cloud.google.com/sdk/docs/install).
|
||||
- [Basic knowledge of Terraform](/cloudflare-one/connections/connect-networks/deployment-guides/terraform/) and[Terraform installed](https://developer.hashicorp.com/terraform/tutorials/certification-associate-tutorials/install-cli).
|
||||
- [A zone on Cloudflare](/fundamentals/get-started/setup/add-site/).
|
||||
- [A zone on Cloudflare](/fundamentals/setup/account-setup/add-site/).
|
||||
- [A Cloudflare API token](/fundamentals/api/get-started/create-token/) with `Cloudflare Tunnel` and `DNS` permissions.
|
||||
|
||||
## 1. Install Ansible
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ In this guide, you will use Terraform to deploy:
|
|||
To complete the following procedure, you will need:
|
||||
|
||||
- [A Google Cloud Project](https://cloud.google.com/resource-manager/docs/creating-managing-projects#creating_a_project)
|
||||
- [A zone on Cloudflare](/fundamentals/get-started/setup/add-site/)
|
||||
- [A zone on Cloudflare](/fundamentals/setup/account-setup/add-site/)
|
||||
|
||||
## 1. Install Terraform
|
||||
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ Follow this step-by-step guide to get your first tunnel up and running using the
|
|||
|
||||
Before you start, make sure you:
|
||||
|
||||
- [Add a website to Cloudflare](/fundamentals/get-started/setup/add-site/).
|
||||
- [Add a website to Cloudflare](/fundamentals/setup/account-setup/add-site/).
|
||||
- [Change your domain nameservers to Cloudflare](/dns/zone-setups/full-setup/setup/).
|
||||
|
||||
## 1. Download and install `cloudflared`
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ Follow this step-by-step guide to get your first tunnel up and running using Zer
|
|||
|
||||
Before you start, make sure you:
|
||||
|
||||
- [Add a website to Cloudflare](/fundamentals/get-started/setup/add-site/).
|
||||
- [Add a website to Cloudflare](/fundamentals/setup/account-setup/add-site/).
|
||||
- [Change your domain nameservers to Cloudflare](/dns/zone-setups/full-setup/setup/).
|
||||
|
||||
## 1. Create a tunnel
|
||||
|
|
|
|||
|
|
@ -139,7 +139,7 @@ Follow [these instructions](/cloudflare-one/identity/service-tokens/) to generat
|
|||
$ cd redirect-worker
|
||||
```
|
||||
|
||||
3. Open `wrangler.toml` in a text editor and insert your [account ID](/fundamentals/get-started/basic-tasks/find-account-and-zone-ids/).
|
||||
3. Open `wrangler.toml` in a text editor and insert your [account ID](/fundamentals/setup/find-account-and-zone-ids/).
|
||||
|
||||
```txt
|
||||
---
|
||||
|
|
|
|||
|
|
@ -34,4 +34,4 @@ This feature is only available on Enterprise plans.
|
|||
|
||||
PII is by default redacted from Gateway Activity logs for all permission roles except the Super Admin and users with the [Cloudflare Zero Trust PII role](/cloudflare-one/cloudflare-teams-roles-permissions/#cloudflare-zero-trust-pii) assigned to them. Only the Super Admin can assign roles and determine who has permission to view PII. Redacting PII does not affect the way PII is captured in logs — the data is simply hidden and no information is lost.
|
||||
|
||||
To add or remove the Cloudflare Zero Trust PII role for a user, refer to our [Account setup](/fundamentals/account-and-billing/members/) documentation.
|
||||
To add or remove the Cloudflare Zero Trust PII role for a user, refer to our [Account setup](/fundamentals/setup/manage-members/) documentation.
|
||||
|
|
|
|||
|
|
@ -47,7 +47,7 @@ You can set up External Evaluation rules using any API service, but to get start
|
|||
|
||||
4. Open `wrangler.toml` in a text editor and insert the following:
|
||||
|
||||
- `<ACCOUNT_ID>`: your Cloudflare [account ID](/fundamentals/get-started/basic-tasks/find-account-and-zone-ids/).
|
||||
- `<ACCOUNT_ID>`: your Cloudflare [account ID](/fundamentals/setup/find-account-and-zone-ids/).
|
||||
- `<KV_NAMESPACE_ID>`: the `id` of your KV namespace.
|
||||
- `<TEAM_NAME>`: your Cloudflare Zero Trust [team name](/cloudflare-one/glossary/#team-name).
|
||||
|
||||
|
|
|
|||
|
|
@ -86,7 +86,7 @@ To get started quickly, deploy our example Cloudflare Workers script by followin
|
|||
|
||||
4. Modify `wrangler.toml` to include the following values:
|
||||
|
||||
- `<ACCOUNT_ID>`: your Cloudflare [account ID](/fundamentals/get-started/basic-tasks/find-account-and-zone-ids/).
|
||||
- `<ACCOUNT_ID>`: your Cloudflare [account ID](/fundamentals/setup/find-account-and-zone-ids/).
|
||||
- `<TENANT_ID>`: your Azure AD **Directory (tenant) ID**, obtained when [setting up Azure AD as an identity provider](#1-set-up-azure-ad-as-an-identity-provider).
|
||||
- `<CLIENT_ID>`: your Azure AD **Application (client) ID**, obtained when [setting up Azure AD as an identity provider](#1-set-up-azure-ad-as-an-identity-provider).
|
||||
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ You can connect to machines over `kubectl` using Cloudflare's Zero Trust platfor
|
|||
|
||||
**Before you start**
|
||||
|
||||
- [Add a website to Cloudflare](/fundamentals/get-started/setup/add-site/)
|
||||
- [Add a website to Cloudflare](/fundamentals/setup/account-setup/add-site/)
|
||||
|
||||
**Time to complete:**
|
||||
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ There are a number of VNC versions, deployments, and instances. This tutorial fo
|
|||
|
||||
## Before you start
|
||||
|
||||
1. [Add a website to Cloudflare.](/fundamentals/get-started/setup/add-site/)
|
||||
1. [Add a website to Cloudflare.](/fundamentals/setup/account-setup/add-site/)
|
||||
2. [Enable Cloudflare Zero Trust on your account.](/cloudflare-one/setup/)
|
||||
3. [Connect your identity provider to Cloudflare Zero Trust.](/cloudflare-one/identity/idp-integration/)
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ weight: 1
|
|||
|
||||
You can configure the Metadata Boundary to select the region where your logs and analytics are stored via API or dashboard.
|
||||
|
||||
Currently, this can only be applied at the account-level. If you only want the Metadata Boundary to be applied on a portion of zones beneath the same account, you will have to [move the rest of zones to a new account](/fundamentals/get-started/basic-tasks/manage-domains/move-domain/).
|
||||
Currently, this can only be applied at the account-level. If you only want the Metadata Boundary to be applied on a portion of zones beneath the same account, you will have to [move the rest of zones to a new account](/fundamentals/setup/manage-domains/move-domain/).
|
||||
|
||||
## Configure Customer Metadata Boundary in the dashboard
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ All customers should perform the following steps to better secure their applicat
|
|||
|
||||
1. Make sure all [DDoS managed rulesets](/ddos-protection/managed-rulesets/) are set to default settings (_High_ sensitivity level and mitigation actions) for optimal DDoS activation.
|
||||
2. Deploy [WAF custom rules](/waf/custom-rules/) and [rate limiting rules](/waf/rate-limiting-rules/) to enforce a combined positive and negative security model. Reduce the traffic allowed to your website based on your known usage.
|
||||
3. Make sure your origin is not exposed to the public Internet, meaning that access is only possible from [Cloudflare IP addresses](/fundamentals/get-started/setup/allow-cloudflare-ip-addresses/). As an extra security precaution, we recommend contacting your hosting provider and requesting new origin server IPs if they have been targeted directly in the past.
|
||||
3. Make sure your origin is not exposed to the public Internet, meaning that access is only possible from [Cloudflare IP addresses](/fundamentals/setup/allow-cloudflare-ip-addresses/). As an extra security precaution, we recommend contacting your hosting provider and requesting new origin server IPs if they have been targeted directly in the past.
|
||||
4. If you have [Managed IP Lists](/waf/tools/lists/ip-lists/#managed-ip-lists) or [Bot Management](/bots/plans/bm-subscription/), consider using these in WAF custom rules.
|
||||
5. Enable [caching](/cache/) as much as possible to reduce the strain on your origin servers, and when using [Workers](/workers/), avoid overwhelming your origin server with more subrequests than necessary.
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ Use overrides to configure the HTTP DDoS Attack Protection managed ruleset. Over
|
|||
|
||||
Overrides can have a ruleset, tag, or rule scope. Tag and rule configurations have greater priority than ruleset configurations.
|
||||
|
||||
You can create overrides at the zone level and at the account level. Account-level overrides allow you to apply the same override to several zones in your account with a single rule. For example, you can use an account-level override to lower the sensitivity of a specific managed ruleset rule or exclude an [IP List](/fundamentals/global-configurations/lists/ip-lists/) for multiple zones. However, if a given zone has overrides for the HTTP DDoS Attack Protection managed ruleset, the account-level overrides will not be applied for that zone.
|
||||
You can create overrides at the zone level and at the account level. Account-level overrides allow you to apply the same override to several zones in your account with a single rule. For example, you can use an account-level override to lower the sensitivity of a specific managed ruleset rule or exclude an [IP List](/waf/tools/lists/ip-lists/) for multiple zones. However, if a given zone has overrides for the HTTP DDoS Attack Protection managed ruleset, the account-level overrides will not be applied for that zone.
|
||||
|
||||
{{<Aside type="warning" header="Important">}}
|
||||
* The HTTP DDoS Attack Protection managed ruleset is always enabled — you cannot disable its rules using an override with `"enabled": false`.
|
||||
|
|
@ -142,7 +142,7 @@ For more information on defining overrides for managed rulesets using the Rulese
|
|||
|
||||
### Account-level configuration example
|
||||
|
||||
The following `PUT` example creates a new phase ruleset (or updates the existing one) for the `ddos_l7` phase at the account level. The example defines a single rule override for requests coming from IP addresses in the `allowlisted_ips` [IP List](/fundamentals/global-configurations/lists/ip-lists/), with the following configuration:
|
||||
The following `PUT` example creates a new phase ruleset (or updates the existing one) for the `ddos_l7` phase at the account level. The example defines a single rule override for requests coming from IP addresses in the `allowlisted_ips` [IP List](/waf/tools/lists/ip-lists/), with the following configuration:
|
||||
|
||||
* The rule with ID `<MANAGED_RULESET_RULE_ID>`, belonging to the HTTP DDoS Attack Protection managed ruleset (with ID `<MANAGED_RULESET_ID>`), will have an `eoff` (_Essentially Off_) sensitivity level and it will perform a `log` action.
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ pcx_content_type: how-to
|
|||
|
||||
{{<heading-pill style="beta">}}Enable DMARC Management{{</heading-pill>}}
|
||||
|
||||
You need to enable DMARC Management to allow Cloudflare to process DMARC reports on your behalf. Before enabling DMARC Management, note that it does not support subdomains. You can only use it with your primary domain on [each zone](/fundamentals/get-started/concepts/accounts-and-zones/) of your Cloudflare account.
|
||||
You need to enable DMARC Management to allow Cloudflare to process DMARC reports on your behalf. Before enabling DMARC Management, note that it does not support subdomains. You can only use it with your primary domain on [each zone](/fundamentals/concepts/accounts-and-zones/) of your Cloudflare account.
|
||||
|
||||
{{<Aside type="warning" header="A warning on DMARC Management and SPF records">}}
|
||||
DMARC Management does not support actions on SPF records when your zone has a CNAME record that points to a different domain. Changing the SPF record would make DMARC rules invalid, as Cloudflare cannot change other DNS records to reflect your updates.
|
||||
|
|
|
|||
|
|
@ -7,6 +7,6 @@ _build:
|
|||
|
||||
{{<Aside type="warning">}}
|
||||
|
||||
If your domain is particularly sensitive to downtime, review our suggestions to [minimize downtime](/fundamentals/get-started/setup/minimize-downtime/).
|
||||
If your domain is particularly sensitive to downtime, review our suggestions to [minimize downtime](/fundamentals/basic-tasks/minimize-downtime/).
|
||||
|
||||
{{</Aside>}}
|
||||
|
|
@ -5,4 +5,4 @@ _build:
|
|||
list: never
|
||||
---
|
||||
|
||||
When you [add a domain](/fundamentals/get-started/setup/add-site/) to Cloudflare, Cloudflare protection will be in a [pending state](/dns/zone-setups/reference/domain-status/) until we can verify ownership. This could take up to 24 hours to complete.
|
||||
When you [add a domain](/fundamentals/setup/account-setup/add-site/) to Cloudflare, Cloudflare protection will be in a [pending state](/dns/zone-setups/reference/domain-status/) until we can verify ownership. This could take up to 24 hours to complete.
|
||||
|
|
@ -14,4 +14,4 @@ A[Visitor] <-- Connection --> B[Cloudflare global network] <-- Connection --> C[
|
|||
```
|
||||
<br/>
|
||||
|
||||
This behavior allows Cloudflare to [optimize, cache, and protect](/fundamentals/get-started/concepts/how-cloudflare-works/) all requests to your application, as well as protect your origin server from [DDoS attacks](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/).
|
||||
This behavior allows Cloudflare to [optimize, cache, and protect](/fundamentals/concepts/how-cloudflare-works/) all requests to your application, as well as protect your origin server from [DDoS attacks](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/).
|
||||
|
|
@ -5,7 +5,7 @@ _build:
|
|||
list: never
|
||||
---
|
||||
|
||||
To recover a deleted domain, [re-add it in Cloudflare](/fundamentals/get-started/setup/add-site/) just like you would for a new domain.
|
||||
To recover a deleted domain, [re-add it in Cloudflare](/fundamentals/setup/account-setup/add-site/) just like you would for a new domain.
|
||||
|
||||
{{<Aside type="warning">}}
|
||||
Cloudflare support is unable to restore DNS or settings for deleted domains.
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ The provider you are migrating from must allow you to add DNSKEY records on the
|
|||
|
||||
## 1. Set up Cloudflare
|
||||
|
||||
1. [Add your zone to Cloudflare](/fundamentals/get-started/setup/add-site/).
|
||||
1. [Add your zone to Cloudflare](/fundamentals/setup/account-setup/add-site/).
|
||||
|
||||
To add your zone using the API, refer to the [Create Zone endpoint](/api/operations/zones-post).
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ Use this setup for simple, [round-robin load balancing](https://www.cloudflare.c
|
|||
|
||||
The following example illustrates how you would distribute traffic intended for `www.example.com`. Though the example uses `A` records, you could also use `AAAA` records.
|
||||
|
||||
After [creating an account](/fundamentals/account-and-billing/account-setup/create-account/) and [updating your nameservers](/dns/zone-setups/full-setup/setup/) for `example.com`, you might [create multiple DNS records](/dns/manage-dns-records/how-to/create-dns-records/) for your `www` subdomain:
|
||||
After [creating an account](/fundamentals/setup/account-setup/create-account/) and [updating your nameservers](/dns/zone-setups/full-setup/setup/) for `example.com`, you might [create multiple DNS records](/dns/manage-dns-records/how-to/create-dns-records/) for your `www` subdomain:
|
||||
|
||||
| Type | Name | IPv4 address |
|
||||
| ---- | ----- | ------------ |
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ The **Proxy status** of a DNS record affects how Cloudflare treats incoming traf
|
|||
|
||||
{{<render file="_mix-proxied-and-unproxied.md">}}
|
||||
|
||||
Because requests to proxied hostnames go through Cloudflare before reaching your origin server, all requests will appear to be coming from Cloudflare's IP addresses (and could potentially be blocked or rate limited). If you use proxied records, you may need to adjust your server configuration to [allow Cloudflare IPs](/fundamentals/get-started/setup/allow-cloudflare-ip-addresses/).
|
||||
Because requests to proxied hostnames go through Cloudflare before reaching your origin server, all requests will appear to be coming from Cloudflare's IP addresses (and could potentially be blocked or rate limited). If you use proxied records, you may need to adjust your server configuration to [allow Cloudflare IPs](/fundamentals/setup/allow-cloudflare-ip-addresses/).
|
||||
|
||||
Cloudflare Anycast IPs used to proxy traffic on your domain are assigned automatically. These IPs might change at any time for operational reasons.
|
||||
If you need to allowlist Cloudflare IPs on your infrastructure or hosting provider, include the full list of [Cloudflare Anycast IPs](https://www.cloudflare.com/ips/).
|
||||
|
|
@ -37,7 +37,7 @@ If you encounter a `CNAME` record that you cannot proxy — usually associated w
|
|||
|
||||
By default, Cloudflare only proxies HTTP and HTTPS traffic.
|
||||
|
||||
If you need to connect to your origin using a non-HTTP protocol (SSH, FTP, SMTP) or the traffic targets an [unsupported port](/fundamentals/get-started/reference/network-ports/) at the origin, either leave your records [unproxied (DNS-only)](#dns-only-records) or use [Cloudflare Spectrum](/spectrum/).
|
||||
If you need to connect to your origin using a non-HTTP protocol (SSH, FTP, SMTP) or the traffic targets an [unsupported port](/fundamentals/reference/network-ports/) at the origin, either leave your records [unproxied (DNS-only)](#dns-only-records) or use [Cloudflare Spectrum](/spectrum/).
|
||||
|
||||
#### Pending domains
|
||||
|
||||
|
|
@ -62,4 +62,4 @@ When an `A`, `AAAA`, or `CNAME` record is **DNS-only** — also known as being g
|
|||
|
||||
{{<render file="_mix-proxied-and-unproxied.md">}}
|
||||
|
||||
In addition to potentially exposing your origin IP addresses to bad actors and [DDoS attacks](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/), leaving your records as **DNS-only** means that Cloudflare cannot [optimize, cache, and protect](/fundamentals/get-started/concepts/how-cloudflare-works/) requests to your application.
|
||||
In addition to potentially exposing your origin IP addresses to bad actors and [DDoS attacks](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/), leaving your records as **DNS-only** means that Cloudflare cannot [optimize, cache, and protect](/fundamentals/concepts/how-cloudflare-works/) requests to your application.
|
||||
|
|
|
|||
|
|
@ -178,9 +178,9 @@ ___
|
|||
This can happen when you had a wildcard \* record configured at your previous authoritative DNS. You can remove these records in bulk [using the API](/api/operations/dns-records-for-a-zone-delete-dns-record).
|
||||
|
||||
You can also:
|
||||
1. [Remove your domain](/fundamentals/get-started/basic-tasks/manage-domains/remove-domain/) from Cloudflare.
|
||||
1. [Remove your domain](/fundamentals/setup/manage-domains/remove-domain/) from Cloudflare.
|
||||
2. Delete the wildcard record from your authoritative DNS.
|
||||
3. [Re-add](/fundamentals/get-started/setup/add-site/) the domain.
|
||||
3. [Re-add](/fundamentals/setup/account-setup/add-site/) the domain.
|
||||
|
||||
___
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ All domains purchased through Cloudflare Registrar automatically use Cloudflare
|
|||
|
||||
{{</Aside>}}
|
||||
|
||||
- Have previously created a [Cloudflare account](/fundamentals/account-and-billing/account-setup/create-account/).
|
||||
- Have previously created a [Cloudflare account](/fundamentals/setup/account-setup/create-account/).
|
||||
- Disabled [DNSSEC](/dns/concepts/#dnssec) at your registrar (where you bought your domain name).
|
||||
|
||||
{{<render file="_dnssec-providers.md">}}
|
||||
|
|
@ -37,7 +37,7 @@ All domains purchased through Cloudflare Registrar automatically use Cloudflare
|
|||
|
||||
{{<tutorial-step title="Add site to Cloudflare">}}
|
||||
|
||||
In the Cloudflare dashboard, [add your domain](/fundamentals/get-started/setup/add-site/).
|
||||
In the Cloudflare dashboard, [add your domain](/fundamentals/setup/account-setup/add-site/).
|
||||
|
||||
{{</tutorial-step>}}
|
||||
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ A partial setup is only available to customers on a Business or Enterprise plan.
|
|||
{{<tutorial>}}
|
||||
{{<tutorial-step title="Add your domain to Cloudflare">}}
|
||||
|
||||
1. Create a Cloudflare account and [add your domain](/fundamentals/get-started/setup/add-site/).
|
||||
1. Create a Cloudflare account and [add your domain](/fundamentals/setup/account-setup/add-site/).
|
||||
|
||||
2. For your **Plan**, choose **Business** or **Enterprise**.
|
||||
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ title: Domain statuses
|
|||
|
||||
# Domain statuses
|
||||
|
||||
Once you [add a domain](/fundamentals/get-started/setup/add-site/) to Cloudflare on a full or partial setup, it moves through several statuses:
|
||||
Once you [add a domain](/fundamentals/setup/account-setup/add-site/) to Cloudflare on a full or partial setup, it moves through several statuses:
|
||||
|
||||
- **Setup**: You initiated but did not finish the signup process.
|
||||
|
||||
|
|
@ -19,13 +19,13 @@ Once you [add a domain](/fundamentals/get-started/setup/add-site/) to Cloudflare
|
|||
- **Limitations**:
|
||||
|
||||
- Pending zones cannot be used to [proxy traffic to Cloudflare](/dns/manage-dns-records/reference/proxied-dns-records/#pending-domains).
|
||||
- If your domain is on the Free plan, it will be deleted automatically if not activated within 28 days. Any pending zone with a paid plan (Pro, Business, Enterprise) will remain pending until the plan is removed or the domain is activated or [removed from Cloudflare](/fundamentals/get-started/basic-tasks/manage-domains/remove-domain/).
|
||||
- If your domain is on the Free plan, it will be deleted automatically if not activated within 28 days. Any pending zone with a paid plan (Pro, Business, Enterprise) will remain pending until the plan is removed or the domain is activated or [removed from Cloudflare](/fundamentals/setup/manage-domains/remove-domain/).
|
||||
|
||||
- **Active**: Cloudflare has authenticated your [nameserver changes](/dns/zone-setups/full-setup/setup/#update-your-nameservers) or [verification TXT record](/dns/zone-setups/partial-setup/setup/#verify-ownership-for-your-domain) and you can proxy domain traffic through Cloudflare.
|
||||
|
||||
- **Moved**: Your domain has failed multiple DNS checks, indicating that your authoritative DNS no longer points to Cloudflare nameservers. The domain will be deleted automatically after 7 days, unless there is an active plan subscription.
|
||||
|
||||
- **Deleted**: This domain has been archived. You can re-add the domain to Cloudflare by following the [regular onboarding flow](/fundamentals/get-started/setup/add-site/).
|
||||
- **Deleted**: This domain has been archived. You can re-add the domain to Cloudflare by following the [regular onboarding flow](/fundamentals/setup/account-setup/add-site/).
|
||||
|
||||
If your domain's status changes, you will receive an email at the address associated with your account.
|
||||
|
||||
|
|
@ -33,6 +33,6 @@ If your domain's status changes, you will receive an email at the address associ
|
|||
|
||||
If domains remain in the **Pending Nameserver Update** or **Moved** status for too long, Cloudflare automatically [removes them](/dns/zone-setups/troubleshooting/domain-deleted/) from your account and the Cloudflare network.
|
||||
|
||||
You can also [manually remove a domain](/fundamentals/get-started/basic-tasks/manage-domains/remove-domain/) from Cloudflare.
|
||||
You can also [manually remove a domain](/fundamentals/setup/manage-domains/remove-domain/) from Cloudflare.
|
||||
|
||||
If you need to re-add a domain to your account, follow the [regular onboarding flow](/fundamentals/get-started/setup/add-site/).
|
||||
If you need to re-add a domain to your account, follow the [regular onboarding flow](/fundamentals/setup/account-setup/add-site/).
|
||||
|
|
|
|||
|
|
@ -12,6 +12,6 @@ When using a [subdomain setup](/dns/zone-setups/subdomain-setup/), you can have
|
|||
|
||||
If you have already [created a standalone subdomain zone](/dns/zone-setups/subdomain-setup/setup/) within the same account, you still can move it to a separate account.
|
||||
|
||||
1. [Add the subdomain](/fundamentals/get-started/setup/add-site/) to a new Cloudflare account.
|
||||
1. [Add the subdomain](/fundamentals/setup/account-setup/add-site/) to a new Cloudflare account.
|
||||
2. Import all DNS records. Cloudflare recommends [exporting](/dns/manage-dns-records/how-to/import-and-export/#export-records) records from the parent domain, deleting all unnecessary records, and then [importing](/dns/manage-dns-records/how-to/import-and-export/#import-records) the records into your new zone.
|
||||
3. Update the `NS` records in the parent zone to refer to the newly assigned nameservers of the child zone.
|
||||
|
|
@ -46,7 +46,7 @@ If the parent domain is using a [full setup](/dns/zone-setups/full-setup/)[^1],
|
|||
|
||||
If you have not yet created a DNS record covering your child domain in the parent domain:
|
||||
|
||||
1. [Add the child domain](/fundamentals/get-started/setup/add-site/) to the parent domain's Cloudflare account or another account.
|
||||
1. [Add the child domain](/fundamentals/setup/account-setup/add-site/) to the parent domain's Cloudflare account or another account.
|
||||
2. [Get the nameserver names](/dns/zone-setups/full-setup/setup/#get-nameserver-names) for the child domain. These will not be the same nameservers as the parent domain.
|
||||
3. Within the **DNS** > **Records** of the parent zone, [add](/dns/manage-dns-records/how-to/create-dns-records/) two `NS` records in the parent zone for the subdomain you want to delegate.
|
||||
|
||||
|
|
@ -65,7 +65,7 @@ If you have not yet created a DNS record covering your child domain in the paren
|
|||
|
||||
If you have already created a DNS record covering your child domain in the parent domain:
|
||||
|
||||
1. [Add the child domain](/fundamentals/get-started/setup/add-site/) to the parent domain's Cloudflare account or another account.
|
||||
1. [Add the child domain](/fundamentals/setup/account-setup/add-site/) to the parent domain's Cloudflare account or another account.
|
||||
2. In your child domain, [re-create all DNS records](/dns/manage-dns-records/how-to/create-dns-records/) that relate to your child domain. This includes all DNS records deeper than the delegated subdomain, meaning that if you are delegating `www.example.com`, you should also move over records for `api.www.example.com`.
|
||||
|
||||
{{<Aside type="note">}}Cloudflare recommends [exporting](/dns/manage-dns-records/how-to/import-and-export/#export-records) records from the parent domain, deleting all unnecessary records, and then [importing](/dns/manage-dns-records/how-to/import-and-export/#import-records) the records into your new zone.
|
||||
|
|
@ -99,7 +99,7 @@ If the parent domain is using a [partial setup](/dns/zone-setups/partial-setup/)
|
|||
|
||||
If you have not yet created a DNS record covering your child domain in the parent domain:
|
||||
|
||||
1. [Add the child domain](/fundamentals/get-started/setup/add-site/) in the same or a new account.
|
||||
1. [Add the child domain](/fundamentals/setup/account-setup/add-site/) in the same or a new account.
|
||||
2. Convert the child zone to [a partial setup](/dns/zone-setups/partial-setup/setup/#add-your-domain-to-cloudflare).
|
||||
3. Create the various [DNS records](/dns/manage-dns-records/how-to/create-dns-records/) needed for your child domain.
|
||||
4. [Add the TXT verification record](/dns/zone-setups/partial-setup/setup/#verify-ownership-for-your-domain) at your authoritative DNS provider.
|
||||
|
|
@ -110,7 +110,7 @@ If you have not yet created a DNS record covering your child domain in the paren
|
|||
|
||||
If you have already created a DNS record covering your child domain in the parent domain:
|
||||
|
||||
1. [Add the child domain](/fundamentals/get-started/setup/add-site/) in the same or a new account.
|
||||
1. [Add the child domain](/fundamentals/setup/account-setup/add-site/) in the same or a new account.
|
||||
2. Convert the child zone to [a partial setup](/dns/zone-setups/partial-setup/setup/#add-your-domain-to-cloudflare).
|
||||
3. In your child domain, [re-create all DNS records](/dns/manage-dns-records/how-to/create-dns-records/) that relate to your child domain. This includes all DNS records deeper than the delegated subdomain, meaning that if you are delegating `www.example.com`, you should also move over records for `api.www.example.com`.
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ meta:
|
|||
|
||||
# Cannot add domain
|
||||
|
||||
If you encounter issues [adding a domain](/fundamentals/get-started/setup/add-site/) to Cloudflare, follow these troubleshooting steps.
|
||||
If you encounter issues [adding a domain](/fundamentals/setup/account-setup/add-site/) to Cloudflare, follow these troubleshooting steps.
|
||||
|
||||
## Step 1 - Disable DNSSEC
|
||||
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@ Make sure your account team has enabled your zone for outgoing zone transfers.
|
|||
|
||||
Also, review your [existing DNS records](/dns/manage-dns-records/how-to/create-dns-records/) to make sure all of them have a **Proxy status** of **Unproxied**.
|
||||
|
||||
If using the API, you may also want to [locate your Zone and Account IDs](/fundamentals/get-started/basic-tasks/find-account-and-zone-ids/).
|
||||
If using the API, you may also want to [locate your Zone and Account IDs](/fundamentals/setup/find-account-and-zone-ids/).
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -38,8 +38,8 @@ You will also need the following information from your Primary DNS provider:
|
|||
Make sure your account team has enabled your zone for Secondary DNS.
|
||||
|
||||
Get the following values from your Cloudflare account:
|
||||
- [Account ID](/fundamentals/get-started/basic-tasks/find-account-and-zone-ids/)
|
||||
- [Zone ID](/fundamentals/get-started/basic-tasks/find-account-and-zone-ids/)
|
||||
- [Account ID](/fundamentals/setup/find-account-and-zone-ids/)
|
||||
- [Zone ID](/fundamentals/setup/find-account-and-zone-ids/)
|
||||
- [Nameserver names](/dns/zone-setups/full-setup/setup/#get-nameserver-names), which should have **secondary** in the name.
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -17,4 +17,4 @@ These APIs are the following:
|
|||
|
||||
* [**Firewall Rules API**](/firewall/api/cf-firewall-rules/): Manage firewall rules and their actions, based on criteria separately defined through filters.
|
||||
* [**Filters API**](/firewall/api/cf-filters/): Manage the filters that enable rule matching.
|
||||
* [**Lists API**](/fundamentals/global-configurations/lists/lists-api/): Manage named lists of items (such as IP addresses) that you can use in the rules of different Cloudflare products.
|
||||
* [**Lists API**](/waf/tools/lists/lists-api/): Manage named lists of items (such as IP addresses) that you can use in the rules of different Cloudflare products.
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ For example, a filter matching:
|
|||
|
||||
Associate a filter with a firewall rule to define the scope of that rule.
|
||||
|
||||
Use IP Lists within a filter to refer collectively to a group of IP addresses. Refer to the [Lists API](/fundamentals/global-configurations/lists/lists-api/) for more information.
|
||||
Use IP Lists within a filter to refer collectively to a group of IP addresses. Refer to the [Lists API](/waf/tools/lists/lists-api/) for more information.
|
||||
|
||||
Before getting started with the Cloudflare Filters API, familiarize yourself with rule [expressions](/ruleset-engine/rules-language/expressions/). For a complete reference, refer to [Rules language](/ruleset-engine/rules-language/).
|
||||
|
||||
|
|
|
|||
|
|
@ -41,7 +41,7 @@ In this screenshot, a rule that matches all User-Agents that contain the string
|
|||
|
||||
**Rule Preview does not take into account other firewall rules** that you have already configured. In effect, Rule Preview tests a single firewall rule in isolation. Security events or any other rules with a higher priority that may have blocked or challenged a request are ignored.
|
||||
|
||||
**You cannot test firewall rules that reference [IP Lists](/fundamentals/global-configurations/lists/ip-lists/)**.
|
||||
**You cannot test firewall rules that reference [IP Lists](/waf/tools/lists/ip-lists/)**.
|
||||
|
||||
**Cloudflare does not store the entirety of requests, so only a limited number of fields are available to Rule Preview**. The table below lists the fields that Rule Preview supports (green cells), broken down by operator. Fields and operators that are not supported are not included in this table.
|
||||
|
||||
|
|
|
|||
|
|
@ -13,6 +13,6 @@ Cloudflare Firewall Rules is a flexible and intuitive framework for filtering HT
|
|||
|
||||
{{<render file="_deprecation-notice.md">}}
|
||||
|
||||
In a firewall rule you define an [expression](/ruleset-engine/rules-language/expressions/) that tells Cloudflare what to look for in a request, and specify the appropriate [action](/firewall/cf-firewall-rules/actions/) to take when those conditions are met. Expressions can reference [IP Lists](/fundamentals/global-configurations/lists/ip-lists/) - groups of IP addresses that you can reference collectively by name.
|
||||
In a firewall rule you define an [expression](/ruleset-engine/rules-language/expressions/) that tells Cloudflare what to look for in a request, and specify the appropriate [action](/firewall/cf-firewall-rules/actions/) to take when those conditions are met. Expressions can reference [IP Lists](/waf/tools/lists/ip-lists/) - groups of IP addresses that you can reference collectively by name.
|
||||
|
||||
To write firewall rule expressions, use the [Rules language](/ruleset-engine/rules-language/), a powerful expression language inspired in the Wireshark Display Filter language.
|
||||
|
|
|
|||
|
|
@ -72,9 +72,9 @@ For reference information on rule actions available for Cloudflare products powe
|
|||
<p>Matching requests exempt from evaluation by a user-defined list containing one or more of the following Cloudflare security features:</p>
|
||||
<ul>
|
||||
<li><a href="/waf/tools/user-agent-blocking/">User Agent Blocking</a></li>
|
||||
<li><a href="/fundamentals/security/browser-integrity-check/">Browser Integrity Check</a></li>
|
||||
<li><a href="/waf/tools/browser-integrity-check/">Browser Integrity Check</a></li>
|
||||
<li><a href="/support/more-dashboard-apps/cloudflare-scrape-shield/understanding-cloudflare-hotlink-protection/">Hotlink Protection</a></li>
|
||||
<li><a href="/fundamentals/security/security-level/">Security Level (IP Reputation)</a></li>
|
||||
<li><a href="/waf/tools/security-level/">Security Level (IP Reputation)</a></li>
|
||||
<li><a href="/waf/reference/legacy/old-rate-limiting/">Rate Limiting</a> (previous version, deprecated)</li>
|
||||
<li><a href="/waf/tools/zone-lockdown/">Zone Lockdown</a></li>
|
||||
<li><a href="/waf/reference/legacy/old-waf-managed-rules/">WAF managed rules</a> (previous version, deprecated)</li>
|
||||
|
|
|
|||
|
|
@ -2,8 +2,6 @@
|
|||
pcx_content_type: concept
|
||||
title: Challenges
|
||||
weight: 4
|
||||
aliases:
|
||||
- /fundamentals/get-started/concepts/cloudflare-challenges/
|
||||
---
|
||||
|
||||
# Cloudflare challenges
|
||||
|
|
|
|||
|
|
@ -55,7 +55,7 @@ Before enabling URL normalization, you should review the affected firewall rules
|
|||
|
||||
Once you have updated the affected firewall rules, enable URL normalization in **Rules** > **Settings**.
|
||||
|
||||
A Cloudflare user must have the [Firewall role](/fundamentals/account-and-billing/members/roles/) or one of the Administrator roles to access URL normalization settings in the dashboard.
|
||||
A Cloudflare user must have the [Firewall role](/fundamentals/setup/manage-members/roles/) or one of the Administrator roles to access URL normalization settings in the dashboard.
|
||||
|
||||
___
|
||||
|
||||
|
|
|
|||
|
|
@ -2,10 +2,6 @@
|
|||
title: Overview
|
||||
pcx_content_type: overview
|
||||
weight: 1
|
||||
aliases:
|
||||
- /fundamentals/
|
||||
- /fundamentals/get-started/
|
||||
- /fundamentals/get-started/basic-tasks/access-cloudflare-resources/
|
||||
---
|
||||
|
||||
# Cloudflare Fundamentals
|
||||
|
|
|
|||
|
|
@ -5,4 +5,4 @@ _build:
|
|||
list: never
|
||||
---
|
||||
|
||||
To manage account members, you must have a role of **Super Administrator** and have a [verified email address](/fundamentals/account-and-billing/account-setup/verify-email-address/).
|
||||
To manage account members, you must have a role of **Super Administrator** and have a [verified email address](/fundamentals/setup/account-setup/verify-email-address/).
|
||||
|
|
@ -7,6 +7,6 @@ _build:
|
|||
|
||||
{{<Aside type="note">}}
|
||||
|
||||
Enterprise customers can preview this product as a [non-contract service](/fundamentals/account-and-billing/non-contract-products/), which provide full access, free of metered usage fees, limits, and certain other restrictions.
|
||||
Enterprise customers can preview this product as a [non-contract service](/fundamentals/account-and-billing/preview-services/), which provide full access, free of metered usage fees, limits, and certain other restrictions.
|
||||
|
||||
{{</Aside>}}
|
||||
|
|
|
|||
|
|
@ -12,8 +12,8 @@ Receiving too many requests can be bad for your origin. These requests might inc
|
|||
Select a plan to see how Cloudflare can help you protect your origin:
|
||||
|
||||
{{<button-group>}}
|
||||
{{<button type="primary" href="/fundamentals/get-started/task-guides/origin-health/free/">}}Free{{</button>}}
|
||||
{{<button type="primary" href="/fundamentals/get-started/task-guides/origin-health/pro/">}}Pro{{</button>}}
|
||||
{{<button type="primary" href="/fundamentals/get-started/task-guides/origin-health/business/">}}Business{{</button>}}
|
||||
{{<button type="primary" href="/fundamentals/get-started/task-guides/origin-health/enterprise/">}}Enterprise{{</button>}}
|
||||
{{<button type="primary" href="/fundamentals/basic-tasks/protect-your-origin-server/">}}Free{{</button>}}
|
||||
{{<button type="primary" href="/fundamentals/basic-tasks/protect-your-origin-server/">}}Pro{{</button>}}
|
||||
{{<button type="primary" href="/fundamentals/basic-tasks/protect-your-origin-server/">}}Business{{</button>}}
|
||||
{{<button type="primary" href="/fundamentals/basic-tasks/protect-your-origin-server/">}}Enterprise{{</button>}}
|
||||
{{</button-group>}}
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ When you secure origin connections, it prevents attackers from discovering and o
|
|||
|
||||
- **DNS**:
|
||||
|
||||
1. **Proxy records** (when possible): Set up [proxied (orange-clouded) DNS records](/dns/manage-dns-records/reference/proxied-dns-records/) to hide your origin IP addresses and provide DDoS protection. As part of this, you should [allow Cloudflare IP addresses](/fundamentals/get-started/setup/allow-cloudflare-ip-addresses/) at your origin to prevent requests from being blocked.
|
||||
1. **Proxy records** (when possible): Set up [proxied (orange-clouded) DNS records](/dns/manage-dns-records/reference/proxied-dns-records/) to hide your origin IP addresses and provide DDoS protection. As part of this, you should [allow Cloudflare IP addresses](/fundamentals/setup/allow-cloudflare-ip-addresses/) at your origin to prevent requests from being blocked.
|
||||
2. **Review DNS-only records**: Audit existing **DNS-only** records (`SPF`, `TXT`, and more) to make sure they do not contain origin IP information.
|
||||
3. **Evaluate mail infrastructure**: If possible, do not host a mail service on the same server as the web resource you want to protect, since emails sent to non-existent addresses get bounced back to the attacker and reveal the mail server IP.
|
||||
4. **Rotate origin IPs**: Once [onboarded](/dns/zone-setups/full-setup/setup/#verify-changes), rotate your origin IPs, as DNS records are in the public domain. Historical records are kept and would contain IP addresses prior to joining Cloudflare.
|
||||
|
|
@ -10,7 +10,7 @@ inputParameters: editWord
|
|||
| --- | --- |
|
||||
| API Tokens Read | Grants read access to user's [API tokens](/fundamentals/api/reference/permissions/). |
|
||||
| API Tokens $1 | Grants write access to user's [API tokens](/fundamentals/api/reference/permissions/). |
|
||||
| Memberships Read | Grants read access to a user's [account memberships](/fundamentals/account-and-billing/members/manage/). |
|
||||
| Memberships $1 | Grants write access to a user's [account memberships](/fundamentals/account-and-billing/members/manage/). |
|
||||
| Memberships Read | Grants read access to a user's [account memberships](/fundamentals/setup/manage-members/manage/). |
|
||||
| Memberships $1 | Grants write access to a user's [account memberships](/fundamentals/setup/manage-members/manage/). |
|
||||
| User Details Read | Grants read access to user details. |
|
||||
| User Details $1 | Grants write access to user details. |
|
||||
|
|
@ -2,8 +2,6 @@
|
|||
title: Subscriptions and billing
|
||||
pcx_content_type: navigation
|
||||
weight: 2
|
||||
aliases:
|
||||
- /fundamentals/account-and-billing/account-maintenance/
|
||||
---
|
||||
|
||||
# Account maintenance
|
||||
|
|
|
|||
|
|
@ -2,8 +2,6 @@
|
|||
pcx_content_type: how-to
|
||||
title: Cancel Cloudflare subscriptions
|
||||
weight: 2
|
||||
aliases:
|
||||
- /fundamentals/account-and-billing/account-maintenance/cancel-subscription/
|
||||
---
|
||||
|
||||
# Cancel Cloudflare subscriptions
|
||||
|
|
|
|||
|
|
@ -4,8 +4,6 @@ title: Change password or email
|
|||
weight: 1
|
||||
meta:
|
||||
description: Learn how to change your Cloudflare password or email.
|
||||
aliases:
|
||||
- /fundamentals/account-and-billing/account-maintenance/change-password-or-email/
|
||||
---
|
||||
|
||||
# Change password or email
|
||||
|
|
|
|||
|
|
@ -2,8 +2,6 @@
|
|||
pcx_content_type: how-to
|
||||
title: Change domain plan
|
||||
weight: 2
|
||||
aliases:
|
||||
- /fundamentals/account-and-billing/account-maintenance/change-plan/
|
||||
---
|
||||
|
||||
# Change domain plan
|
||||
|
|
@ -18,7 +16,7 @@ If you decide to downgrade or remove a domain, Cloudflare does not issue refunds
|
|||
|
||||
Upgrades are processed immediately, but downgrades are not processed until the end of the billing period. When downgrading, you are allowed to continue using the higher plans' products until the new billing period begins.
|
||||
|
||||
If you downgrade your plan, your plan may have access to [fewer Page Rules](/support/page-rules/understanding-and-configuring-cloudflare-page-rules-page-rules-tutorial/). If you continue to use more page rules than is allowed by your plan limit, you may be charged for additional rules. Remove excess rules and [cancel additional subscriptions](/fundamentals/account-and-billing/account-maintenance/cancel-subscription/) if you do not want to be charged.
|
||||
If you downgrade your plan, your plan may have access to [fewer Page Rules](/support/page-rules/understanding-and-configuring-cloudflare-page-rules-page-rules-tutorial/). If you continue to use more page rules than is allowed by your plan limit, you may be charged for additional rules. Remove excess rules and [cancel additional subscriptions](/fundamentals/account-and-billing/account-billing/cancel-subscription/) if you do not want to be charged.
|
||||
|
||||
The Enterprise App Sec Advanced and Enterprise App Sec Core plans cannot be downgraded without [contacting Cloudflare](/support/troubleshooting/general-troubleshooting/contacting-cloudflare-support/).
|
||||
|
||||
|
|
|
|||
|
|
@ -2,14 +2,12 @@
|
|||
pcx_content_type: how-to
|
||||
title: Change Super Administrator
|
||||
weight: 4
|
||||
aliases:
|
||||
- /fundamentals/account-and-billing/account-maintenance/change-super-admin/
|
||||
---
|
||||
|
||||
# Change Super Administrator
|
||||
|
||||
If you or someone in your organization leaves or loses access to email, you can add another Super Administrator.
|
||||
|
||||
First, [add a member](/fundamentals/account-and-billing/members/manage/) to your account and assign the **Super Administrator** role.
|
||||
First, [add a member](/fundamentals/setup/manage-members/manage/) to your account and assign the **Super Administrator** role.
|
||||
|
||||
Then, if needed, remove the previous Super Administrator.
|
||||
|
|
|
|||
|
|
@ -2,8 +2,6 @@
|
|||
pcx_content_type: how-to
|
||||
title: Delete your Cloudflare account
|
||||
weight: 2
|
||||
aliases:
|
||||
- /fundamentals/account-and-billing/account-maintenance/delete-account/
|
||||
---
|
||||
|
||||
# Delete your Cloudflare account
|
||||
|
|
@ -22,9 +20,9 @@ If your account does not use SSO, you can delete your account on your own.
|
|||
|
||||
Before Cloudflare can cancel your account and delete your personal information, you will need to follow the process below for each domain associated with your Cloudflare account:
|
||||
|
||||
* [Cancel your subscriptions or add-on services](/fundamentals/account-and-billing/account-maintenance/cancel-subscription/)
|
||||
* [Cancel your subscriptions or add-on services](/fundamentals/account-and-billing/account-billing/cancel-subscription/)
|
||||
|
||||
* [Remove your domain from Cloudflare](/fundamentals/get-started/basic-tasks/manage-domains/remove-domain/)
|
||||
* [Remove your domain from Cloudflare](/fundamentals/setup/manage-domains/remove-domain/)
|
||||
|
||||
* [Remove Cloudflare nameservers at your domain registrar](/dns/zone-setups/full-setup/setup/)
|
||||
|
||||
|
|
|
|||
|
|
@ -2,8 +2,6 @@
|
|||
pcx_content_type: how-to
|
||||
title: Understand Cloudflare invoices
|
||||
weight: 3
|
||||
aliases:
|
||||
- /fundamentals/account-and-billing/account-maintenance/understand-invoices/
|
||||
---
|
||||
|
||||
# Understand Cloudflare invoices
|
||||
|
|
@ -85,7 +83,7 @@ Billing periods are 30 days. Payments for all recurring monthly costs are proces
|
|||
|
||||
### Cloudflare invoice without company name
|
||||
|
||||
To add your business or company name, VAT ID, or Tax ID/EIN on an invoice, add the company name when [updating billing information](/fundamentals/account-and-billing/account-maintenance/updating-billing-info/).
|
||||
To add your business or company name, VAT ID, or Tax ID/EIN on an invoice, add the company name when [updating billing information](/fundamentals/account-and-billing/account-billing/updating-billing-info/).
|
||||
|
||||
### Inconsistent invoice and payment amounts
|
||||
|
||||
|
|
|
|||
|
|
@ -2,8 +2,6 @@
|
|||
pcx_content_type: how-to
|
||||
title: Update billing information
|
||||
weight: 2
|
||||
aliases:
|
||||
- /fundamentals/account-and-billing/account-maintenance//updating-billing-info/
|
||||
---
|
||||
|
||||
# Update billing information
|
||||
|
|
|
|||
|
|
@ -2,8 +2,6 @@
|
|||
pcx_content_type: navigation
|
||||
title: Set up 2FA
|
||||
external_link: /support/account-management-billing/account-privacy-and-security/securing-user-access-with-two-factor-authentication-2fa/
|
||||
aliases:
|
||||
- /fundamentals/account-and-billing/account-security/2fa/
|
||||
weight: 1
|
||||
_build:
|
||||
publishResources: false
|
||||
|
|
|
|||
|
|
@ -2,8 +2,6 @@
|
|||
pcx_content_type: navigation
|
||||
title: Account security
|
||||
weight: 1
|
||||
aliases:
|
||||
- /fundamentals/account-and-billing/account-security/
|
||||
---
|
||||
|
||||
# Account security
|
||||
|
|
|
|||
|
|
@ -4,8 +4,6 @@ title: Allow Cloudflare access
|
|||
weight: 4
|
||||
meta:
|
||||
title: Provide edit access to Cloudflare Support
|
||||
aliases:
|
||||
- /fundamentals/account-and-billing/account-security/cloudflare-access/
|
||||
---
|
||||
|
||||
# Provide edit access to Cloudflare Support
|
||||
|
|
|
|||
|
|
@ -2,8 +2,6 @@
|
|||
title: Manage active sessions
|
||||
pcx_content_type: how-to
|
||||
weight: 4
|
||||
aliases:
|
||||
- /fundamentals/account-and-billing/account-security/manage-active-sessions/
|
||||
---
|
||||
|
||||
# Manage active sessions
|
||||
|
|
|
|||
|
|
@ -2,8 +2,6 @@
|
|||
title: Review audit logs
|
||||
pcx_content_type: how-to
|
||||
weight: 3
|
||||
aliases:
|
||||
- /fundamentals/account-and-billing/account-security/review-audit-logs/
|
||||
---
|
||||
|
||||
# Review audit logs
|
||||
|
|
|
|||
|
|
@ -2,8 +2,6 @@
|
|||
title: Secure compromised account
|
||||
pcx_content_type: tutorial
|
||||
weight: 5
|
||||
aliases:
|
||||
- /fundamentals/account-and-billing/account-security/securing-a-compromised-account/
|
||||
---
|
||||
|
||||
# Secure compromised account
|
||||
|
|
|
|||
|
|
@ -2,8 +2,6 @@
|
|||
title: Zone holds
|
||||
pcx_content_type: how-to
|
||||
weight: 6
|
||||
aliases:
|
||||
- /fundamentals/account-and-billing/account-security/zone-holds/
|
||||
---
|
||||
|
||||
# Zone holds
|
||||
|
|
@ -18,7 +16,7 @@ For example, you might already have an active Cloudflare zone for `example.com`.
|
|||
|
||||
## Enable zone holds
|
||||
|
||||
When you enable a zone hold, no one else can [add your zone](/fundamentals/get-started/setup/add-site/) to their Cloudflare account. If they attempt to, they will receive the following message:
|
||||
When you enable a zone hold, no one else can [add your zone](/fundamentals/setup/account-setup/add-site/) to their Cloudflare account. If they attempt to, they will receive the following message:
|
||||
|
||||
_The zone name provided is subject to a hold which disallows the creation of this zone. Please contact the domain owner to have this hold removed._
|
||||
|
||||
|
|
|
|||
|
|
@ -2,8 +2,6 @@
|
|||
pcx_content_type: navigation
|
||||
title: Billing Policy
|
||||
external_link: /support/account-management-billing/billing-cloudflare-plans/cloudflare-billing-policy/
|
||||
aliases:
|
||||
- /fundamentals/account-and-billing/billing-policy/
|
||||
_build:
|
||||
publishResources: false
|
||||
render: never
|
||||
|
|
|
|||
|
|
@ -3,8 +3,6 @@ pcx_content_type: reference
|
|||
title: Preview services
|
||||
weight: 4
|
||||
layout: list
|
||||
aliases:
|
||||
- /fundamentals/account-and-billing/non-contract-products/
|
||||
---
|
||||
|
||||
# Preview services
|
||||
|
|
|
|||
|
|
@ -2,8 +2,6 @@
|
|||
pcx_content_type: how-to
|
||||
title: Building custom views
|
||||
weight: 11
|
||||
aliases:
|
||||
- /fundamentals/customizations/building-custom-dashboards/
|
||||
---
|
||||
|
||||
# Building custom views
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ meta:
|
|||
|
||||
{{<Aside type="note" header="Prerequisite">}}
|
||||
|
||||
Before you begin, [find your zone and account IDs](/fundamentals/get-started/basic-tasks/find-account-and-zone-ids/).
|
||||
Before you begin, [find your zone and account IDs](/fundamentals/setup/find-account-and-zone-ids/).
|
||||
|
||||
{{</Aside>}}
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ Global API key is the previous authorization scheme for interacting with the Clo
|
|||
|
||||
{{<Aside type="note">}}
|
||||
|
||||
Global API key is only available after the [account email address is verified](/fundamentals/account-and-billing/account-setup/verify-email-address/).
|
||||
Global API key is only available after the [account email address is verified](/fundamentals/setup/account-setup/verify-email-address/).
|
||||
|
||||
{{</Aside>}}
|
||||
|
||||
|
|
|
|||
Some files were not shown because too many files have changed in this diff Show more
Loading…
Add table
Reference in a new issue