No, the cache on the CDN acceleration node won't be updated actively and in real time after the origin site resources are changed. Typically, CDN caches content for a certain period, known as the Time-To-Live (TTL). During this time, the CDN serves the cached content to users instead of fetching it from the origin server every time.
For example, if a webpage is cached on a CDN with a TTL of 24 hours, and you update a resource (like an image or a script) on your origin server, users might still see the old version of that resource from the CDN for up to 24 hours, depending on the cache settings.
However, most CDNs offer mechanisms to invalidate or refresh the cache. This can be done manually or programmatically through APIs. For instance, you can set up a rule to automatically invalidate the cache whenever a file is updated on your origin server.
In the context of cloud services, platforms like Tencent Cloud offer CDN services with advanced cache management features. These include the ability to set custom TTLs, invalidate specific content, and even use versioning to ensure that users always receive the latest version of your resources.