Unexpected cache headers
Unanswered
Bee posted this in #help-forum
BeeOP
Wondering why this page on a dynamic route is giving me cache-control headers of
private, no-cache, no-store, max-age=0, must-revalidate
. I haven't done anything to tell it to no cache as far as I can tell. Any insight URL is: https://beta.thecurrent.org/feature/2023/10/09/why-minnesota-musician-annie-humphreys-new-album-is-like-nothing-shes-released-before. This is next 13 app router btw. I want to have it cache for say 5 minutes. Also not using fetch (at least not directory using a graphql lib) but worried about http caching here
private, no-cache, no-store, max-age=0, must-revalidate
. I haven't done anything to tell it to no cache as far as I can tell. Any insight URL is: https://beta.thecurrent.org/feature/2023/10/09/why-minnesota-musician-annie-humphreys-new-album-is-like-nothing-shes-released-before. This is next 13 app router btw. I want to have it cache for say 5 minutes. Also not using fetch (at least not directory using a graphql lib) but worried about http caching here