Clarify custom hostname routing for Worker as origin #27424
Merged
Conversation
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
Addresses the lack of clarity about how custom hostname traffic reaches Workers when using Cloudflare for SaaS. Changes: - Add new section explaining how custom hostname traffic flows through the SaaS zone - Provide concrete example showing the relationship between SaaS zone, fallback origin, custom hostname, and Worker route - Clarify that wildcard route pattern (*/*) automatically captures custom hostname traffic - Rewrite step 4 with clearer routing options and examples - Add related resources section linking to hostname routing and Workers routes docs Fixes #27397
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
Contributor
|
Preview URL: https://579d000e.preview.developers.cloudflare.com Files with changes (up to 15) |
* Added case of only some hostnames to worker * Removed copied line
dinasaur404
approved these changes
Jan 6, 2026
ravindra-dyte
pushed a commit
to dyte-io/cloudflare-docs
that referenced
this pull request
Jan 7, 2026
* Clarify custom hostname routing for Worker as origin Addresses the lack of clarity about how custom hostname traffic reaches Workers when using Cloudflare for SaaS. Changes: - Add new section explaining how custom hostname traffic flows through the SaaS zone - Provide concrete example showing the relationship between SaaS zone, fallback origin, custom hostname, and Worker route - Clarify that wildcard route pattern (*/*) automatically captures custom hostname traffic - Rewrite step 4 with clearer routing options and examples - Add related resources section linking to hostname routing and Workers routes docs Fixes cloudflare#27397 * Added case of only some hostnames to worker (cloudflare#27425) * Added case of only some hostnames to worker * Removed copied line --------- Co-authored-by: Isak Wang Gustavsen <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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
Addresses the lack of clarity about how custom hostname traffic reaches Workers when using Cloudflare for SaaS.
*/*) automatically captures custom hostname trafficFixes #27397