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
I have a question regarding the scope of impact when a Cache Poisoning issue occurs in Next.js. Based on the changes, it seems that when revalidate is unintentionally set to 1, SSR pages that should not be cached are being cached.
In this situation, is the cached content limited to the specific route path? For example, if there are paths aaa/a and aaa/b, and the issue occurs on aaa/a, will the previously cached rendering result of aaa/a only be visible on aaa/a, or could it also be exposed on aaa/b?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Summary
I have a question regarding the scope of impact when a Cache Poisoning issue occurs in Next.js. Based on the changes, it seems that when revalidate is unintentionally set to 1, SSR pages that should not be cached are being cached.
In this situation, is the cached content limited to the specific route path? For example, if there are paths aaa/a and aaa/b, and the issue occurs on aaa/a, will the previously cached rendering result of aaa/a only be visible on aaa/a, or could it also be exposed on aaa/b?
Please help me. Thank you.
Reference:
Additional information
No response
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions