-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Forced refresh method #1998
Forced refresh method #1998
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's not what reloadDocument
does. It tells React Router to bypass client side routing. Probably all you need to do is remove the cache control headers. But don't remove the canonical URL headers!
I'm currently trying that but it continues to load the old version. Wouldn't we want to avoid the client side routing in this case? My thought being that we need to make the request to the server to get the new data Edit: It behaves as expected when I include the reloadDocument, but doesn't appear to have any effect if I remove the cache control header |
No. Try this: https://remix.run/docs/en/main/route/should-revalidate |
This now works as expected with that function added |
Resolves #1996
Still testing, the removal of the caching headers may be unnecessary