Bugfix: fetching feed data caching problem fix #24
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This implementation adds a unique identifier to the URL of the API route to force a cache-busting reload. The
Cache-Control, Pragma,
andExpires
headers are also added to the response to disable caching for dynamic content.By adding a unique identifier to the URL, you can ensure that the URL is unique and not cached by the CDN or any intermediary caches. In this implementation, the current timestamp is used as the unique identifier.
You can add this code to the existing code in the
app/api/prompt/route.js
file to fix the issue with the API route returning a cached prompts array.