Continuing the discussion from Cache incorrectly serving old content under specific conditions:
(sorry, I don’t see a way to add a new message to the existing topic)
As far as I see, the different edge nodes have the different age objects at this moment and some of them have a different Content-Length. However, I don’t see anything specifically outstanding that hints the different cache nodes are sending different objects in the VCL. If this is not expected and they’d like to submit a ticket for us, we are more than happy to assist to sort this out.
Sorry, I’m not used to fastly terminology, so I have no idea of what VCL is.
My idea is that the cache must be aware of that the original file was updated and cached content should be updated as long as the master is online. There may be delay, but definitely not a month long one. If that’s the case, there is a problem on fastly side because old file has stuck in the the cache (probably just a single node) for a month, despite that the original has updated multiple times.
Or is the logic different and if the file is cached it won’t be updated unless it expires? If that’s the case, the TTL of 1 month is definitely a misconfiguration.
Please sign in to leave a comment.