kv-asset-handler

Same except I go POST and version the assets. It's a super fun and awesome way to manage sites IMO. The idea is what Worker Sites [1] do via KV Asset Handler [2]. Would love to see your code for signed Payload / auth. Or, just hear how you do it. My auth is a bit... weak. Cheers. [1] https://developers.cloudflare.com/workers/platform/sites [2] https://github.com/cloudflare/kv-asset-handler

Exactly. Little more clarification here though I think... Flexibility of Cloudflare KV reads in general still yield quick enough results and make doing a quick and dirty cache a pretty good use case IMHO. But Worker Sites specifically also use the Cloudflare Worker Cache runtime API — aka, per each POP, first reads of a route (index.html, blah.css, cat.jpg) are from KV and THEN cached indefinitely cutting that time to like 10ms. This is taken then even further by using ETAG matching to make BrowserTTL indefinite (304s not 200s) on all assets until cleared cutting repeat visitors (regardless of POP) to basically nothing. Though .html for some reason doesn’t respect this (I think...). Which to me is a GREAT deal! Cache Object: https://developers.cloudflare.com/workers/runtime-apis/cache Asset Mapper: https://github.com/cloudflare/kv-asset-h