Though I notice the HTML for / is not being cached, if this is not dynamic then you may consider add
Though I notice the HTML for / is not being cached, if this is not dynamic then you may consider adding rules or code to cache HTML as well
Cache-Control headers are presentcf-cache-status: HIT? Because that's a whole other question.Increasing the cache TTL will keep those caches around for longer but increase time to revalidate when you push new updates.why would it increase time to revalidate if asset (JS/CSS) paths are going to be changed anyway as the name (paths) of those files changes everytime the project is bundled. assuming the index.html containing those asset paths remains dynamic (not cached)
env.STATIC_ASSET_CDN_ORIGIN an R2 public bucket with Custom Domain?cf properties to the fetch requestCf-Cache-Status: HIT headerfavicon ? maybe its because content-type is not provided for this css asset? its still odd. i dont see this behaviour for traditional websites network request flows
cf-cache-status: HIT