How to handle cached loaders when doing optimistic UI?

[reloadedhead]

Hi all,

I'd like to apologise beforehand if this has already been discussed. I was not able to find it the repo. My question is how to handle cached loader responses (using cache-control directives) and optimistic UI.

I have faced the following situation:

1. Be on /items, with the loader's response cached, using an etag based on a hashed string of the stringified array of items.
2. Delete an item with action in /items. Follow optimistic UI pattern checking for corresponding data in formData, and filtering out deleted item.
3. Have the action delete the item, but on loader revalidation, browser uses the cached version, which still contains the deleted item.

Deletion is just a button wrapped in a useFetcher form.

I've tried busting the cache with a redirect response after deletion, with the cache-control directive none with no success (which kinda makes sense...). I feel there's something from the web platform I am missing.