You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You have on landing page link to example which uses "latest" tag in package.json and everything is okay.
When I migrate app to 3.0.0-rc.6 there is a problem with correct caching headers.
With example from landing on production build I see the following headers:
With production build and all default values for caching it should return the following header: Cache-Control: s-maxage=31536000, stale-while-revalidate
The text was updated successfully, but these errors were encountered:
Description
You have on landing page link to example which uses "latest" tag in package.json and everything is okay.
When I migrate app to
3.0.0-rc.6
there is a problem with correct caching headers.With example from landing on production build I see the following headers:
Cache-Control: s-maxage=31536000, stale-while-revalidate
But with rc6 header is:
Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate
Of course, this makes app very slow because nextjs doesn't cache ssr, etc and recalculates everything on each request.
I build a small example with rc6 which after yarn run build and yarn start on main page gives this wrong cache-control header.
Mandatory reproduction URL (CodeSandbox or GitHub repository)
https://github.com/max-frai/nextintl-cache-problem
Reproduction description
Steps to reproduce:
Expected behaviour
With production build and all default values for caching it should return the following header:
Cache-Control: s-maxage=31536000, stale-while-revalidate
The text was updated successfully, but these errors were encountered: