Hi, @jifarris. My guesses for a root cause are either TTL (time to live) issues or a service worker.
Our support team can tell you for certain if you send us the x-nf-request-id header for the incorrect response.
In order to troubleshoot this, 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 which we send 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
If you prefer, a HAR file recording of the incorrect response will also contain that information (including the x-nf-request-id and all the other details above as well). Please feel free to send the HAR file if you prefer.
If there are any questions we are happy to answer.