Skip to content

Conversation

@dinasaur404
Copy link
Contributor

Summary

  • Add a page to document how to route custom hostnames/subdomain traffic to the dispatch worker

  • Document o2o traffic behavior with routes

Screenshots (optional)

image

Documentation checklist

@hyperlint-ai
Copy link
Contributor

hyperlint-ai bot commented Jul 1, 2025

Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment.

We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally.


PR Change Summary

Added a new page to document hostname routing for custom domains and subdomains, including setup instructions and routing behavior.

  • Introduced a new page on hostname routing for dispatch workers.
  • Documented setup instructions for routing custom hostnames and subdomains.
  • Explained Orange-to-Orange (o2o) traffic behavior and its implications.

Added Files

  • src/content/docs/cloudflare-for-platforms/workers-for-platforms/get-started/hostname-routing.mdx

How can I customize these reviews?

Check out the Hyperlint AI Reviewer docs for more information on how to customize the review.

If you just want to ignore it on this PR, you can add the hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add hyperlint-ignore to the PR to ignore the link check for this PR.

@github-actions
Copy link
Contributor

github-actions bot commented Jul 1, 2025

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern Owners
/src/content/docs/cloudflare-for-platforms/workers-for-platforms/ @irvinebroque, @angelampcosta, @GregBrimble, @cloudflare/deploy-config, @cloudflare/pcx-technical-writing


If you're only looking to route subdomain records (e.g. `customer1.saas.com`), you can use a more specific route (`*.saas.com/*`) to route requests to your dispatch Worker.

### Setup
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

think accidentally commented out? or someting weird with format?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Set

@dinasaur404 dinasaur404 merged commit 3db7a18 into production Jul 1, 2025
11 checks passed
@dinasaur404 dinasaur404 deleted the add-hostname-routing-page branch July 1, 2025 18:55
sdnts pushed a commit to sdnts/cloudflare-docs that referenced this pull request Jul 24, 2025
* Add hostname routing documentation for Workers for Platforms

* Fix broken links in hostname routing page

* Update hostname-routing.mdx
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants