Having an interesting situation with a browser based tool. In Edge, browsing around the tool/site will build up the cache, and pages will pull from the cache and load quickly when returning to them. In Chrome, it seems after clicking around to a few pages, Chrome is dropping old cache items (i.e. the page we were on 3 or 4 clicks ago), and does not pull from cache, resulting in slower loads. Not trying to troubleshoot the slower loads (those are a separate thread due to VDI and other variables outside of current scope), just find a way to force Chrome to keep all of those cache items and pull from them for longer. It was already communicated out that Chrome was the "preferred browser" for the tool, so trying to see if this is a hidden setting in Chrome that can change the behavior, or I just need to tell them to change to Edge (and thus retest all functionality, this time using that browser).
![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
Forcing Chrome browser to cache (and keep the cache) for a site
- Thread starter ThatITGuy
- Start date
modi123
Supreme [H]ardness
- Joined
- Sep 6, 2006
- Messages
- 7,217
Are these pages 3 or 4 clicks back static or dynamic with the data shown?
Are the page under your domain of influence, or just any ol' random ones?
Are the page under your domain of influence, or just any ol' random ones?
This kinda sounds like caching directives are not present from serverside response, or directives are being honored in slightly different ways depending on the browser.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control