If your site is purely static then I would recommend pages
If your site is purely static then I would recommend pages

#<Response> could not be cloned.? I have error logging with Sentry but I'm pretty sure the stack trace is not accurate -.-await this.state.storage.put(foo, bar);example.com/page* is the only way to support https://example.com/page?blah=1, but it also matches https://example.com/page1234. This seems like a pretty serious limitation.Route pattern matching considers the entire request URL, including the query parameter string. Since route patterns may not contain query parameters, the only way to have a route pattern match URLs with query parameters is to terminate it with a wildcard, *.So I doubt it would change anytime too soon.
return fetch(request) the request, wouldn't interfere with anything but would cause Worker Invocations still
/post* to go to a worker but not /posts?ggg, if you made a route for /posts* service none, that should be more specific and stop the Worker from running on that path
#<Response> could not be cloned.await this.state.storage.put(foo, bar);example.com/page*https://example.com/page?blah=1https://example.com/page1234return fetch(request)/post*/posts*