[Bug?]: Cloudflare presets don't cache assets

[rvlzzr]

Duplicates

• I have searched the existing issues

Latest version

• I have tested the latest version

Current behavior 😯

In solid-start 0.3 using the cloudflare adapters, refreshing the page and looking at the network section of devtools, you see assets all showing (memory cache) as expected.

In the current version, everything hits the server which returns 304 status.

Expected behavior 🤔

Assets should be cached.

Steps to reproduce 🕹

Steps:

1. Use one of the cloudflare presets and build/deploy.
2. Open network tab of devtools in your browser.
3. Refresh the page.
4. Note that you never see memory or disk cache for assets.

Context 🔦

No response

Your environment 🌎

No response

[rvlzzr]

Also routeRules as per nksaraf/vinxi#140 (comment) don't seem to do anything for Cloudflare as far as I can tell -- I don't see any working way to send cache-control headers for assets that works with the cloudflare adapters (and shouldn't this be the default anyway?).

[ryansolid]

Hmm.. we might have done something special for our previous adapters but now we follow nitro's preset. So the advice from nksaraf/vinxi#140 (comment) is the solution. If that doesn't work it is on Nitro/Vinxi side but there isn't anything we can do here.