The docs are a little confusing on the Static Assets Workers, maybe I'm misreading them but they see

The docs are a little confusing on the Static Assets Workers, maybe I'm misreading them but they seem to contract themselves.

If you read https://developers.cloudflare.com/workers/static-assets/routing/ it says:

When a request invokes a Worker with assets:

If a request is found with a matching path to the current route requested then that asset will always be served.

When a request invokes a Worker with assets:

If a request is found with a matching path to the current route requested then that asset will always be served.

When a request invokes a Worker with assets:

If a request is found with a matching path to the current route requested then that asset will always be served.

When a request invokes a Worker with assets:

If a request is found with a matching path to the current route requested then that asset will always be served.

I tested it, and if a static asset is matched, it's returned, else my Worker's fetch is invoked. Makes sense. Then I got confused by the binding example on https://developers.cloudflare.com/workers/static-assets/binding/:

export default {
  async fetch(request, env) {
    const url = new URL(request.url);
    if (url.pathname.startsWith("/api/")) {
      // TODO: Add your custom /api/* logic here.
      return new Response("Ok");
    }
    // Otherwise, serve the static assets.
    // Without this, the Worker will error and no assets will be served.
    return env.ASSETS.fetch(request);
  },
};

export default {
  async fetch(request, env) {
    const url = new URL(request.url);
    if (url.pathname.startsWith("/api/")) {
      // TODO: Add your custom /api/* logic here.
      return new Response("Ok");
    }
    // Otherwise, serve the static assets.
    // Without this, the Worker will error and no assets will be served.
    return env.ASSETS.fetch(request);
  },
};

export default {
  async fetch(request, env) {
    const url = new URL(request.url);
    if (url.pathname.startsWith("/api/")) {
      // TODO: Add your custom /api/* logic here.
      return new Response("Ok");
    }
    // Otherwise, serve the static assets.
    // Without this, the Worker will error and no assets will be served.
    return env.ASSETS.fetch(request);
  },
};

export default {
  async fetch(request, env) {
    const url = new URL(request.url);
    if (url.pathname.startsWith("/api/")) {
      // TODO: Add your custom /api/* logic here.
      return new Response("Ok");
    }
    // Otherwise, serve the static assets.
    // Without this, the Worker will error and no assets will be served.
    return env.ASSETS.fetch(request);
  },
};

But I don't think that's true / the final return won't ever be hit if a static asset is found, it would just never call the worker (e.g. you have public/blog.html, and

/blog

/blog

/blog

/blog is hit, it will just return the static asset and not call the worker). Am I missing something? It feels like the final "return" should really be a 404? Which I think technically it would return anyway but to me at least it's a bit misleaading as for assets that exist, it'd never hit the worker anyway

nejc•9/30/24, 11:40 AM

hi all

Quick question

nejc•9/30/24, 11:40 AM

When request comes into the worker you have two objects (context and environment). Is environment scoped to the specific reqeust like context or is shared across the requests? Example if I set some unique value on environment, will it stay in that request or it can leak into other requests. Afaik context is scoped to the request and is not leaking (like global scope) across requests in the same worker, but I am not sure if the same is for environment

ac•9/30/24, 1:55 PM

Any chance we'll get Build watch paths for Workers anytime soon? The new CI/CD setup is awesome, but there are a lot of unnecessary builds happening with a monorepo

ac•9/30/24, 2:43 PM

(and if I'm going to have to pay for builds, I need to be able to control that or it won't be usable

)

AAshley The docs are a little confusing on the Static Assets Workers, maybe I'm misreadi...

Wonky Onion•9/30/24, 3:25 PM

Yeah you’re totally right. The final asset binding call is intended to invoke 404/not found handling behaviour from your worker, e.g return index.html for a SPA, or whatever you’ve set to 404.html. I’ll get the docs updated to reflect that better - thanks for catching that!

WWonky Onion Yeah you’re totally right. The final asset binding call is intended to invoke 40...

AshleyOP•9/30/24, 3:38 PM

Thank you, and glad I’m not going mad

AshleyOP•9/30/24, 5:05 PM

I think this is a bit more nuanced with static assets workers now. As static assets that are served via a static asset worker behave in the same way as static assets on Pages: free, unlimited and (potentially) served from cache - it won’t hit the worker, in a traditional way, anyway - it will either be served as a static asset (and not hit the worker) or served from cache.

AshleyOP•9/30/24, 5:08 PM

(“Not hit the worker” might not be the best wording, as not sure of the underlying implementation, or if you see logs and things - not checked - but it can presumably hit cache for static assets before the worker… nothing in the docs though like there is for Pages)

Harold Anderson•9/30/24, 6:12 PM

Should I use Workers or Pages Functions? I see that Pages and Workers are merging, but I don't know which one is going away. Thanks.

Original message was deleted

AshleyOP•9/30/24, 6:21 PM

Good to know, that would still mean there is now cache before a worker, technically - I know there’s many levels to caching with reserve / tiered cache etc but before I think there was 0 cache before workers, there’s now at least something that could be hit

HHarold Anderson Should I use Workers or Pages Functions? I see that Pages and Workers are mergi...

AshleyOP•9/30/24, 6:23 PM

Pages is merging into Workers, but Pages likely exists for a long time as there’s a lot that uses it I would suspect. To help you choose, there’s a matrix here: https://developers.cloudflare.com/workers/static-assets/compatibility-matrix/ (but there’s no time period for merging etc known yet)

Cloudflare Docs

Workers vs. Pages (compatibility matrix) | Cloudflare Workers docs

Compatibility matrix for asset hosting on Cloudflare Workers and Pages.

Original message was deleted

AshleyOP•9/30/24, 6:24 PM

Yup, but still - my point was just that “workers execute before cache” that used to always be true now has a nuance

AAshley Pages is merging into Workers, but Pages likely exists for a long time as there’...

Harold Anderson•9/30/24, 6:26 PM

So if I am starting a Svelte project, for instance, I should use Workers and the https://github.com/sveltejs/kit/tree/main/packages/adapter-cloudflare-workers instead of the adapter-cloudflare, which is for Pages with Functions.

GitHub

kit/packages/adapter-cloudflare-workers at main · sveltejs/kit

web development, streamlined. Contribute to sveltejs/kit development by creating an account on GitHub.

AshleyOP•9/30/24, 6:30 PM

My message got deleted

But I’d say that’s a good idea (CF docs: https://developers.cloudflare.com/workers/frameworks/framework-guides/svelte/). Keep in mind it is in beta, so maybe some bugs, but as betas go, it’s probably pretty stable.

AAshley My message got deleted 😭 But I’d say that’s a good idea (CF docs: https://devel...

Harold Anderson•9/30/24, 6:32 PM

Is there any support for Svelte 5?

AshleyOP•9/30/24, 6:33 PM

That I do not know

AAshley Good to know, that would still mean there is now cache before a worker, technica...

Chaika•9/30/24, 6:35 PM

not normal cache, it'd just be kv. Still correct to say there's no cache before Workers

AAshley That I do not know 😅

Harold Anderson•9/30/24, 6:36 PM

Thank you. Svelte 5 is a total rewrite of Svelte 4 but is supposed to be backward compatible. However, Svelte 4 is being gently discouraged. Just trying to avoid writing obsolete code from day 1.

CChaika not normal cache, it'd just be kv. Still correct to say there's no cache before ...

AshleyOP•9/30/24, 6:42 PM

I think you can argue this both ways. If we look at how things were before - there was no cache, all requests hit the worker - that’s not quite true now. There is another mechanism now, with static assets, that means your worker won’t be hit. Whether it’s KV or otherwise is an implementation detail, imo.

AAshley I think you can argue this both ways. If we look at how things were before - the...

Chaika•9/30/24, 6:43 PM

You can say not all requests will result in worker invocations sure, still no cache though

Chaika•9/30/24, 6:44 PM

if you wanted to be more specific you could say no cache of worker results but ehh the fact KV internally talks to cache service is an implementation detail

AshleyOP•9/30/24, 6:51 PM

That’s fair, I think this is probably a Cloudflare-specific case where it’s a little cloudy (excuse the pun) - as if I was storing something in KV as part of my Worker, I’d say KV is caching, same as Redis in a non-CF architecture. But with CF having so many caching mechanisms, perhaps it’s better to be explicit and say KV rather than cache for Static Asset workers - thanks for the chat, fun to discuss these things

AAshley That’s fair, I think this is probably a Cloudflare-specific case where it’s a li...

Chaika•9/30/24, 6:55 PM

I mean to me the root of it is just that even if you use kv in your worker you can't cache your worker result and avoid an invocation. Static Assets are entirely free, kv cache hit or not

Mmono_cron So I'm looking at the workers KV docs and I see no way to perform bulk operation...

Chaika•9/30/24, 6:57 PM

not possible via binding atm although it's been requested a fair few times

CChaika I mean to me the root of it is just that even if you use kv in your worker you c...

AshleyOP•9/30/24, 6:58 PM

I agree, but it's not the same as it was before - before it was all workers, every single request, and that's just the distinction that I think is important/needs to be clear. KV, imo, is a form of cache, so I think it's fair to say that for static assets, they are not invoking your worker, and they are (potentially) being returned from cache (which is KV, so you can't control the cache unlike other cache products). What I was getting at with the cache stuff is within Cloudflare specifically there's a lot of heavy-lifting done by the word cache (tiered, reserve etc.) versus in general software engineering, it's a pretty generic term (e.g. you could cache in memory and you're caching, in say a Rails app)

Chaika•9/30/24, 6:59 PM

yea it's def not same as before. With Pages you could even cache function results (or double cache static) on custom domain if you wanted as well which was interesting

AshleyOP•9/30/24, 7:00 PM

I think there used to be a diagram somewhere but I can't find it that explained all the caches, where they sit, and the order of execution - maybe it was on a blog. If someone has an up-to-date version of that, that'd be mega handy (including this new stuff with static assets workers)

AAshley I think there used to be a diagram somewhere but I can't find it that explained ...

Chaika•9/30/24, 7:00 PM

explained all the caches?

Chaika•9/30/24, 7:01 PM

There's general request flow chart but I've never seen anything about all the caches I don't think

AshleyOP•9/30/24, 7:01 PM

Maybe I dreamt it

Chaika•9/30/24, 7:01 PM

really not that many anyway unless you want to try to get deep into dns cache/workers being kept warm/etc

AshleyOP•9/30/24, 7:02 PM

Do you have a link to that general request flow chart by chance?

Chaika•9/30/24, 7:02 PM

right side of specific dash pages like waf if you have big enough of a screen

AshleyOP•9/30/24, 7:03 PM

Thank you

Chaika•9/30/24, 7:03 PM

https://blog.cloudflare.com/building-cloudflare-on-cloudflare/ there is some other diagrams from blogs like

Chaika•9/30/24, 7:05 PM

oh actually there is flow charts for the tiered caches https://blog.cloudflare.com/introducing-cache-reserve/, if you want to include all of the different types of the normal http caches it gets more complex, like
Local -> Tiered Cache Middle -> Tiered Cache Upper -> Cache Reserve -> Origin
and then if you want to get really complex I believe Cache Reserve lives in Pingora while local (and maybe tiered cache too?) just live in other more local services, one of the reasons why cache api is local only afaik

AshleyOP•9/30/24, 7:07 PM

This is awesome, thank you!

Chaika•9/30/24, 7:10 PM

yea there is a lot of layers of http cache, and the rest is more messy. KV is local/tiered. Workers Cache API is just local. R2 Custom Domains just local too, probably same thing for Pages Custom Domains but I've never checked

Chaika•9/30/24, 7:12 PM

yea might just be a general cf for saas thing

DiamondDragon•9/30/24, 7:21 PM

any chance someone can take a look at this? it was reported before and a fix was deployed so not sure why i am experiencing this issue

workers-and-pages-helpError on remote worker: APIError: A request to the Cloudflare API

o7•9/30/24, 7:35 PM

is there a way to get 1 worker to run on GET requests and another worker to run other methods? (not via custom routes either)

o7•9/30/24, 7:38 PM

ra•10/1/24, 1:05 AM

Hi all, I'm using workers and would like to work around the "Simultaneous outgoing
connections/request" limit. Am I able to invoke another worker via service bindings to fan out the requests across multiple workers?

Rra Hi all, I'm using workers and would like to work around the "Simultaneous outgoi...

Cyb3r-Jak3•10/1/24, 1:08 AM

You can not.
From https://developers.cloudflare.com/workers/platform/limits/#simultaneous-open-connections

Simultaneous Open Connections are measured from the top-level request, meaning any connections open from Workers sharing resources (for example, Workers triggered via Service bindings) will share the simultaneous open connection limit.

Cloudflare Docs

Limits | Cloudflare Workers docs

Cloudflare Workers plan and platform limits.

CCyb3r-Jak3 You can not. From https://developers.cloudflare.com/workers/platform/limits/#sim...

ra•10/1/24, 1:14 AM

I submitted a request to raise my limit, but never heard back. Has anyone had success in lifting this limit?

Rra I submitted a request to raise my limit, but never heard back. Has anyone had su...

Cyb3r-Jak3•10/1/24, 1:15 AM

I'd imagine not.

Rra I submitted a request to raise my limit, but never heard back. Has anyone had su...

Isaac McFadyen•10/1/24, 1:21 AM

I believe (not completely sure but highly likely) that the limit is Cloudflare-wide, meaning it's an underlying limit that is built into the Workers runtime and not a limit that can be easily increased per customer.

The docs are a little confusing on the Static Assets Workers, maybe I'm misreading them but they see

Similar Threads

Similar Threads

Similar Threads