I’ve got a site deployed to:
https://amazing-heyrovsky-3732f2.netlify.app/locations/abc
On the route locations/abc I am rendering content that’s editable by the Netlify CMS. When a user edits the content then it gets deployed.
Now the issue I’m running into is that the content there is being cached both in browser and through Netlify. That cache is not expiring.
From the Safari browser I get the response headers:
:status: 200
Content-Type: text/html; charset=utf-8
ETag: "14fc-lryUBJ6q6KOZYEOBXqGRntrAS+Y-df"
Age: 1035
Date: Mon, 25 Oct 2021 00:22:24 GMT
Content-Encoding: br
Content-Length: 1519
Cache-Control: s-maxage=31536000, stale-while-revalidate
Vary: Accept-Encoding
Server: Netlify
x-powered-by: Next.js
x-nf-request-id: 01FJTE6YZH5BQ5EGPJAP2KTR2D
Noticing the ETag which is 14fc-lryUBJ6q6KOZYEOBXqGRntrAS+Y-df
From Curl I get the headers:
age: 580
cache-control: s-maxage=31536000, stale-while-revalidate
content-encoding: gzip
content-length: 1714
content-type: text/html; charset=utf-8
date: Mon, 25 Oct 2021 00:25:17 GMT
etag: "1506-9mnbUKI8+Gi/zjgyQuUBHL93Y/I-df"
server: Netlify
vary: Accept-Encoding
x-nf-request-id: 01FJTDYAEVNS3E2WFT5AT2EYNC
x-powered-by: Next.js
Which is a different ETag of 1506-9mnbUKI8+Gi/zjgyQuUBHL93Y/I-df
So I can tell the responses are different, but not only that, the actual deployed content should be different from both of those caches. Order of content “freshness” Safari (most old) > Curl > Current content.
So from what I can tell there’s an issue with the caching of the response and I can’t tell how/what I’m meant to clear.
If anyone could help that would be fantastic, and if you need any more details just ask and I’m happy to provide as much as possible