<@1155837905143603240> <@459755459117711362> I've been exploring the same use-case, wanting worker r
@Dikshant Rai @Hello, I’m Allie! I've been exploring the same use-case, wanting worker routes functionality for my CF Pages app. The example you provided:
It makes sense, but not a big fan of needing a Pages app at my root domain that needs to account for the routing of all URL paths currently under that domain.
For my case, www.garmin.com is my root domain and we have 100s and 100s of URL paths/routes under www.garmin.com. It would be much easier for us to implement CF Pages apps as "leaf node" apps on certain URL paths using something like the workers routes request mapping functionality instead of using 1 top-level CF Pages app on www.garmin.com that we need to route all URL paths for garmin.com through and determine if they go to Pages or if they should be served by origin or elsewhere.
Is there anyone on the CF Pages team we could raise this feature request to (the ability to map URL patterns to a CF Pages app, enabling CF Pages to be executed based on the route of an incoming request similar to how Workers Routes work)?
It makes sense, but not a big fan of needing a Pages app at my root domain that needs to account for the routing of all URL paths currently under that domain.
For my case, www.garmin.com is my root domain and we have 100s and 100s of URL paths/routes under www.garmin.com. It would be much easier for us to implement CF Pages apps as "leaf node" apps on certain URL paths using something like the workers routes request mapping functionality instead of using 1 top-level CF Pages app on www.garmin.com that we need to route all URL paths for garmin.com through and determine if they go to Pages or if they should be served by origin or elsewhere.
Is there anyone on the CF Pages team we could raise this feature request to (the ability to map URL patterns to a CF Pages app, enabling CF Pages to be executed based on the route of an incoming request similar to how Workers Routes work)?
