Clarify wildcard route matching behavior

[ask-bonk]

The changes look good. Here's a summary of what was added to the "Hostnames may optionally begin with *" section:

1. A caution admonition explaining that * matches zero or more of any character (not just subdomain separators), so *example.com will match hostnames like myexample.com that aren't actually subdomains of example.com. It recommends using two separate routes (example.com/* and *.example.com/*) if you only want to match the domain and its subdomains.

2. A comparison table with 4 example URLs showing the difference between *example.com/* and *.example.com/*:

   • example.com — matched by * prefix, not by *. prefix
   • www.example.com/path — matched by both
   • myexample.com — matched by * prefix (the surprising case from the issue), not by *. prefix
   • not-example.com — matched by neither (because it doesn't end with example.com)

Closes #25763

github run

[github-actions]

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

Pattern	Owners
/src/content/docs/workers/	@cloudflare/workers-docs, @GregBrimble, @irvinebroque, @mikenomitch, @korinne, @WalshyDev, @cloudflare/deploy-config, @cloudflare/pcx-technical-writing, @cloudflare/wrangler, @mattietk

[github-actions]

Preview URL: https://f7d53c5a.preview.developers.cloudflare.com
Preview Branch URL: https://opencode-issue25763-20260206110907.preview.developers.cloudflare.com

Files with changes (up to 15)

Original Link	Updated Link
https://developers.cloudflare.com/workers/configuration/routing/routes/	https://opencode-issue25763-20260206110907.preview.developers.cloudflare.com/workers/configuration/routing/routes/