Server side component with force-dynamic/force-no-store is caching on history.state.
Unanswered
Texas leafcutting ant posted this in #help-forum
Texas leafcutting antOP
When navigating from page to page, it uses dispatchNavigateAction(), this respects the dynamic components, but when a history popstate event happens it uses dispatchTraverseAction(), which restores the page from the cache. Is that intentional? Should that not check if the component is dynamic then re-fetch it? If I run router.refresh() just before I navigate away from the initial page, it gives me the correct version when I return, but as I understand it, I'm asking that I don't cache at all. Is that how it should be working?