The behavior of Cache-Control about workers-sdk HOT 3 OPEN

hello @SukkaW and @surjikal! I'm working on getting this repo updated this week and beginning to resolve some of the long-standing issues here - I appreciate you both taking the time to write in this ticket. the vast majority of people on our team who maintained this project no longer work at CF, so it's been in a bit of limbo since then, sorry about that!

that being said - although this project has some documentation issues and could use some more clarity, especially around things like caching, it is very much safe to use in production. we've been using it heavily in our marketing and documentation sites in the workers/pages ecosystem. I absolutely understand your frustration, but just want to add some perspective for anyone else who might stumble upon this issue 👍

with that out of the way - let's work on how we can make this better! I'm going to remove this from our upcoming milestone release, which will focus on cloudflare/kv-asset-handler#133 and some other related fixes. if there are people who have been involved in this issue and have since dived deeper into caching work, I'd love to work with you on building better documentation around the things you've mentioned in this issue.

we have a #workers-sites channel in our Discord server that would be a great place to sync up on this stuff too: here's an invite link if anyone would like to come in and chat. thanks!

from workers-sdk.

This is still all very confusing for me, and the docs are sparse regarding best practices for caching.

from workers-sdk.

This is still all very confusing for me, and the docs are sparse regarding best practices for caching.

@surjikal I have already given up this sh***y package. The package shouldn't be used under any circumstances (especially don't use it in your production):

• Lacks detailed documentation
• Not actively maintained
  • Many issues not being answered
  • Many PR not being merged nor reviewed
• The original developer even believes in typeof can be used to determine the Error type.
• I used to be a Cloudflare Enterprise Plan customer, and it is what Cloudflare Support Engineer responded to my issue earlier (which leads to me opening a Pull Request myself in cloudflare/kv-asset-handler#100):

If you still want to use the Cloudflare Workers Page, DO NOT use kv-assets-handler, implement your own kv handler instead.

from workers-sdk.