Hey @fool, I’ve created a video to show what’s happening. I haven’t worked with the HAR file yet.
But the video explicitly shows a private navigation window having this issue.
I hope this one is useful as well… I’ve added some comments, to explain what we are talking about. It’s six minutes, but I hope you can give me better insights on why/what/… is happening with your better understanding of how CDN’s work (and better internal understanding of the platform).
Here is the video… I was ‘lucky’ enough to have someone in our team have it and guide him to what I believe would be a way to debug it, or at least try to understand it better:
Start full video link: debug session commented - YouTube
Time of opening private navigation window: around 4:27 which was most surprising to me…
I’ll try to get a reproduction with this HAR file as well. But for me the part where it feels like there is something happening that feels like a ‘race-condition’. So my first thought was the edge servers. But as you established in the previous answers, that shouldn’t be the case.
Thanks for your time @fool. Much appreciated. Hoping to get this sorted out pretty quickly since it has been eating at our conversions for at least a few weeks.
EXTRA INFO: (Just because I have the feeling it could be relevant)
- We are using both the _redirects file and the redirects inside the TOML.
- We are using
./node_modules/.bin/netlify deploy --site $NETLIFY_SITE_ID --auth $NETLIFY_ACCESS_TOKEN --dir=out --prod
to push it online
- There was some time overlap where it could be possible that 2 builds were deploying at the same time from Circle CI
- We have the feeling this issue is from between 3 weeks and a month and half (although it feels more frequently in the past 2 weeks)
[edit]: @fool, added links to two har files related to the request. This time it’s another file for which it is happening, but equally important. With the same breaking result for the end user:
Looking forward to your feedback!
… The more I look at this, the more I start to have the feeling the redirects might have to do with it. (it says serving from disk cache… For a file that should be fetched. So I guess that must be saved in some weird way and make it more permanent, so that the (hard) refresh doesn’t work??)
But for sure wouldn’t want to point you into the wrong direction, so it’s better to follow your own guts on this one for sure!