I've noticed an issue with public share links: when I update the original content, the shared page doesn't reflect the changes immediately. It appears to be cached either by a CDN or your servers. Even a hard reload or adding query parameters (like ?v=2) doesn't force the latest version to load. Only opening the link in an incognito window seems to bypass the cache.

This makes it difficult to share live-updating content, especially when sharing drafts or collaborative documents.

Feature request:

Please consider adding a way to:

Manually refresh or invalidate the cache for a public share link

Or, append a query parameter to force fresh rendering (?nocache=1, for example)

Or, at least provide a setting to reduce caching duration for shared content