CD
Cloudflare Developers•4w ago
aleclarson

Serve static assets from root path, then handle /api/ requests with my worker?

I was hoping the "Static assets" feature could help me simplify my setup (currently Pages + Workers). I'm having trouble with wrangler dev currently. I want to serve static assets (stored in public directory on filesystem) for every request except for /api/ requests, which my worker should handle.
5 Replies
aleclarson
aleclarsonOP•4w ago
I tried these things together: - pass --route "xyz.example.com/api/*" to wrangler dev - set directory = "public" in the [assets] section of my wrangler.toml But my worker is still being invoked for non /api/ requests. This part is a bit confusing:
In the event a request does not match a static asset, and there is no Worker script (or that Worker script calls fetch() on the assets binding), not_found_handling determines how Cloudflare will construct a response.
It says "…and there is no Worker script". But doesn't a worker script always exist when using the Static Assets feature? Aww, I was really hoping this would work: 
routes = [
  "xyz.example.com/api/*",
  { pattern = "xyz.example.com/*", zone_name = "assets.local" }
]
routes = [
  "xyz.example.com/api/*",
  { pattern = "xyz.example.com/*", zone_name = "assets.local" }
]
(in wrangler dev) Am I forced to deploy two workers for this use case? Might as well use Pages at that point, I suppose..
Chaika
Chaika•4w ago
By default, anything that matches a static asset skips your worker, and everything else hits it So you don't pay for static asset hits/they don't invoke your worker, but you can have your worker api as well you can pass the request to the static assets binding in your worker if it doesn't match a static asset and invokes it, to invoke the default 404 behavior: return await env.ASSETS.fetch(request);
aleclarson
aleclarsonOP•4w ago
Right, yet I'm using single-page-application setting, so HTML pages other than / end up hitting the worker first, sadly. Yeah I'm trying to avoid the worker invocation for static assets I'm thinking of using Pages and Pages Functions instead of Workers
Chaika
Chaika•4w ago
It's a long way off but eventually Pages will be moved to Workers Assets (and with a solid migration plan)
aleclarson
aleclarsonOP•4w ago
Please see if my use case is being tracked internally. Thank you 😺 For now, I'll go with Pages. Thanks for the help!

Did you find this page helpful?