I think you may try with any cache busting technique, so to avoid completely the cache. "Cache bus
I think you may try with any cache busting technique, so to avoid completely the cache.
"Cache busting is a technique used in web development to ensure that the latest version of a file is fetched from the server, bypassing cached versions. By appending a unique identifier like a version number or timestamp to the file’s URL, the browser treats it as a new resource, fetching the most up-to-date version. This technique prevents users from seeing outdated cached content and improves the overall user experience."
You may, for example, include the timestamp somewhere in the fetch req. so it will be a unique request.
Why are you using revalidateTag? I myself coudnt make options like (cache : "no-store) work, but revalidatePath/revalidateTag, seemed to work... is the same happening to you?
"Cache busting is a technique used in web development to ensure that the latest version of a file is fetched from the server, bypassing cached versions. By appending a unique identifier like a version number or timestamp to the file’s URL, the browser treats it as a new resource, fetching the most up-to-date version. This technique prevents users from seeing outdated cached content and improves the overall user experience."
You may, for example, include the timestamp somewhere in the fetch req. so it will be a unique request.
Why are you using revalidateTag? I myself coudnt make options like (cache : "no-store) work, but revalidatePath/revalidateTag, seemed to work... is the same happening to you?
