Repository navigation
Conversation
dknecht
requested review from
a team,
baubuchon-cf and
lgarofalo
as code owners
November 3, 2026 02:49
Contributor
AI Review✅ Reviewed Commands
|
Contributor
Review coverage🟡 1 ownership area needs approval. Suggested reviewers: @baubuchon-cf @lgarofalo
CODEOWNERS mappings for displayed areas (1)
|
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://dane-pages-custom-domain-tls.previews.developers.cloudflare.com (commit 904e911)This URL reflects your latest Preview deploymentPreview Deployments by commit
|
Contributor
|
Worker Preview URL: https://gh-dane-pages-custom-domain-tls.previews.developers.cloudflare.com Files with changes (up to 15) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The Cloudflare Pages section of Compliance and vulnerabilities says zone-level TLS and cipher suite settings apply to a Pages custom domain. They do not. A Pages custom domain is a custom hostname on the project's
<project>.pages.devzone, and its certificate and TLS settings are set by Pages when the hostname is created. The Minimum TLS Version and cipher suites of the zone that contains the custom domain are not inherited.This also makes the page contradict four other SSL pages, which already say these settings cannot be configured for Pages hostnames:
ssl/edge-certificates/additional-options/minimum-tls.mdxssl/edge-certificates/additional-options/cipher-suites/troubleshooting.mdxssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/api.mdxssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/dashboard.mdxThe change:
*.pages.dev.Internal evidence: CUSTESC-14456 (Pages engineering confirmed that hostname TLS settings are set by the Pages API and not inherited from the zone), BANDA-1543, CUSTESC-57881, and CUSTESC-61879 (customers whose zone cipher settings did not apply to their Pages custom domains). Follow-up from DEE-3981.
Documentation checklist