diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin.mdx index 9967c47e214f7d..659755340a4e39 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin.mdx @@ -10,8 +10,6 @@ import { GlossaryTooltip, Render } from "~/components" - - ## Requirements To use a custom origin server, you need to meet the following requirements: @@ -25,6 +23,8 @@ To use a custom origin, select that option when [creating a new custom hostname] ## SNI rewrites + + When Cloudflare establishes a connection to your default origin server, the `Host` header and SNI will both be the value of the original custom hostname. However, if you configure that custom hostname with a custom origin, the value of the SNI will be that of the custom origin and the `Host` header will be the original custom hostname. Since these values will not match, you will not be able to use the [Full (strict)](/ssl/origin-configuration/ssl-modes/full-strict/) on your origins. diff --git a/src/content/plans/index.json b/src/content/plans/index.json index ee73b10c4cb8c6..d76e5652f6a77c 100644 --- a/src/content/plans/index.json +++ b/src/content/plans/index.json @@ -2779,6 +2779,13 @@ "biz": "Yes", "ent": "Yes" }, + "sni_rewrite": { + "title": "[SNI Rewrite for Custom Origin](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin/#sni-rewrites)", + "free": "No", + "pro": "No", + "biz": "No", + "ent": "Contact your account team" + }, "custom_certificates": { "title": "[Custom certificates](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/)", "free": "No",