Redirect Routes Don't Follow Caching Rules in Chrome 97
See original GitHub issueLibrary Affected: workbox-webpack-plugin (GenerateSW)
Browser & Platform: Google Chrome 97
Issue or Feature Request Description:
If a redirect route is matched via urlPattern
it is being served by the service worker regardless of the caching strategy. I believe it is a result of this addition in Chrome 97: https://chromestatus.com/feature/5752539724120064#details
Issue Analytics
- State:
- Created 2 years ago
- Reactions:6
- Comments:9 (3 by maintainers)
Top Results From Across the Web
How can I make Chrome stop caching redirects? - Super User
Open the Developer Tools panel ( option command i on Mac, or ctrl shift i on Windows) · Click and hold the reload...
Read more >Set Chrome policies for users or browsers - Google Support
You can enforce Chrome policies from your Admin console that apply to: User accounts to sync policies and preferences across a user's devices....
Read more >How do we control web page caching, across all browsers?
Chrome. Our requirement came from a security test. After logging out from our website you could press the back button and view cached...
Read more >151170 - chrome caches 302 redirect that shouldn't be cached
Clearing the cache fixed the issue. ... The requested resource resides temporarily under a different URI. Since the redirection might be altered ...
Read more >A Guide to Caching with NGINX and NGINX Plus
The parameters to the proxy_cache_path directive define the following settings: The local disk directory for the cache is called /path/to/cache/ ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@wanderview @jeffposnick I can confirm my issue has been resolved in the latest canary build. Thanks for your help!
Likely due to this bug which is fixed in canary:
https://bugs.chromium.org/p/chromium/issues/detail?id=1286367