To ensure that returning customers see updated content, you can consider adjusting the caching settings for the different types of content in your Content Delivery Network (CDN). Here’s how you might update the caching settings based on the provided information:
- Static Content (Images, CSS):
- Change the caching duration from 7 days to a shorter period, depending on how frequently your static content is updated. For example, you might set it to 1 day or a few hours.
- Scripts (Not dependent on the session):
- Decrease the caching duration from 2 hours to a shorter period, such as 30 minutes or even less if your scripts are updated frequently.
- Content Delivery (page.ss):
- Reduce the caching duration from 5 minutes to a shorter timeframe, like 1 minute or less, to ensure that updated content is delivered more quickly.
- Cache Invalidation Request:
- Continue using the Cache Invalidation Request form to manually clear the CDN cache when you want to force an immediate update. This is particularly useful for critical updates that need to be reflected instantly.
- Browser Cache:
- Although the browser cache is not directly controlled by the CDN, you can implement cache-busting techniques in your application to ensure that the browser fetches fresh content. This might include versioning your static files or appending query parameters with a version number.
- CDN Cache Expiry:
- If possible, configure your CDN to automatically refresh static content more frequently than every two hours. Adjust the CDN cache expiry time to align with the frequency of updates on your website.
By adjusting these settings, you can strike a balance between optimizing performance through caching and ensuring that returning customers see the latest content. Keep in mind that the specific steps may vary depending on the CDN provider you are using, so refer to your CDN’s documentation for detailed instructions on how to configure caching settings.