Skip to content

[SaaS] Update custom-origin.mdx #20869

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 20, 2025
Merged

[SaaS] Update custom-origin.mdx #20869

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3edbd1c
[SaaS] Update custom-origin.mdx
ngayerie Mar 17, 2025
2d14cab
Apply suggestion from code review
RebeccaTamachiro Mar 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions ...are-for-platforms/cloudflare-for-saas/start/advanced-settings/custom-origin.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,8 @@ Choose how your custom hostname populates the SNI value with SNI rewrites:

* Currently, SNI Rewrite is not supported for wildcard custom hostnames. Subdomains covered by a wildcard custom hostname send the custom origin server name as the SNI value.

* In the [O2O context](/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/how-it-works/) (when requests are originating from a proxied hostname on zone also on Cloudflare), altering the SNI value to use host header is currently not supported.

* SNI overrides defined in an [Origin Rule](/rules/origin-rules/) will take precedence over SNI rewrites.

* SNI Rewrite usage is subject to the [Service-Specific Terms](https://www.cloudflare.com/service-specific-terms-application-services/#ssl-for-saas-terms).
Expand Down