Skip to content

Commit eee8fdb

Browse files
authored
[SSL] Update custom-origin.mdx
1 parent b3df98f commit eee8fdb

File tree

1 file changed

+2
-2
lines changed
  • src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings

1 file changed

+2
-2
lines changed

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,6 @@ import { GlossaryTooltip, Render } from "~/components"
1010

1111
<Render file="custom-origin-server-definition" />
1212

13-
<Render file="ssl-for-saas-plan-limitation" />
14-
1513
## Requirements
1614

1715
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]
2523

2624
## SNI rewrites
2725

26+
<Render file="ssl-for-saas-plan-limitation" />
27+
2828
When Cloudflare establishes a connection to your default origin server, the `Host` header and <GlossaryTooltip term="Server Name Indication (SNI)">SNI</GlossaryTooltip> will both be the value of the original custom hostname.
2929

3030
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.

0 commit comments

Comments
 (0)