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
{{ message }}
This repository has been archived by the owner on Aug 31, 2021. It is now read-only.
In my localhost for a cacheFirst strategy if "maxAgeSeconds" option is set for the custom cache , it is never getting expired after the defined interval and always getting the old cached response.
Also made sure in my cached response the date header is present
Also the indexedDB contains the exact timestamp of the requested url.
Below is the sw-toolbox version detail
"sw-toolbox" : "^3.6.1"
Below is the sample code were the caching strategy is applied.
In my localhost for a cacheFirst strategy if "maxAgeSeconds" option is set for the custom cache , it is never getting expired after the defined interval and always getting the old cached response.
Also made sure in my cached response the date header is present
Also the indexedDB contains the exact timestamp of the requested url.
Below is the sw-toolbox version detail
"sw-toolbox" : "^3.6.1"
Below is the sample code were the caching strategy is applied.
toolbox.router.get(/sam/v1/productDetails/k-21225F91386049$/, toolbox.cacheFirst,{
cache: {
name: 'product details cache',
maxAgeSeconds: 5
}
});
The text was updated successfully, but these errors were encountered: