Primary domain cache problem

Hi, @pedromartin, I’m seeing this site using a service worker. This is the most likely reason for this behavior. You’ll need to uninstall the service worker locally to resolve that issue.

There is more information about this at the topic link below:

If you believe that Netlify is sending the wrong version, we need to be able to track the HTTP response with this issue. The simplest way to do this is to send us the x-nf-request-id header with every HTTP response.

There more information about this header here:

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

Again, I don’t think x-nf-request-id header will be required though as I’m 99.9% certain this is the service worker doing this. (I’m 100% certain there is a service worker.) If there are other questions about this, please let us know.

1 Like