Next.js standalone - After page update my site sometimes serves previous page version
Unanswered
American Goldfinch posted this in #help-forum
American GoldfinchOP
I'm using a standalone and page router setup with docker. Each time I make a change, It rebuilds it into a docker image and then it deploys it.
I'm using Nginx as my reverse proxy.
What happens is that after I deploy, I navigate to the site where I'm met with the changes I've made. But if I change to a different route (dashboard-> calendar) and then go back (calendar ->dashboard), the old page version shows up (i.e. different components, different layout etc). It helps when I clear the cache, but the thing is, that's not something I can tell my users about all the time.
It seems like the browser is using cached content of the site, which should be cleared automatically right? It just feels weird, like I'm missing something. Is there a way to revalidate the cache so the clients automatically fetch new content from the server?
I'm using Nginx as my reverse proxy.
What happens is that after I deploy, I navigate to the site where I'm met with the changes I've made. But if I change to a different route (dashboard-> calendar) and then go back (calendar ->dashboard), the old page version shows up (i.e. different components, different layout etc). It helps when I clear the cache, but the thing is, that's not something I can tell my users about all the time.
It seems like the browser is using cached content of the site, which should be cleared automatically right? It just feels weird, like I'm missing something. Is there a way to revalidate the cache so the clients automatically fetch new content from the server?