Hi, @shill, if you override our caching this can mean that a local browser (not our CDN) will cache and load content that is no longer up to date. Note, if that is done, you control those changes not us.
If you do see out of date content coming from our CDN, we are happy to troubleshoot that. In those cases, we need a way to identify the request that was incorrect. To do this, we most often use the x-nf-request-id
response header.
There is more information about this header in the support guide below:
If that header isn’t available for any reason, please send the information it replaces (or as many of these details as possible). Those details are:
- the complete URL requested
- the IP address for the system making the request
- the IP address for the CDN node that responded
- the day of the request
- the time of the request
- the timezone the time is in
To summarize, if you changed the headers, the local browser might be caching out of date content as a result. If so, if you stop using those cache-control headers and use our etag header instead for cache invalidation (which is automatic) it should resolve the issue. If you send us the x-nf-request-id
for an out of date response, we can tell you more about why it happened.
If there are other questions, please include them at any time.