SCDN for communities: public caching and signed-in access
Public posts, member pages, search and posting need different cache and security checks.
Contents of this article
Guests and members may receive different content
A forum homepage may include public posts, unread counts, restricted sections and a username. Determine whether personalization is loaded separately or embedded in the HTML before allowing shared caching.
Search and posting have different traffic patterns
Search consumes database resources, posting writes data, and avatars are mainly distribution traffic. Observe each path separately and protect recovery and account-support flows while controlling abusive searches or repeated submissions.
Verify edge copies after moderation
Deleting a post or changing permissions at the origin does not prove every cached copy has changed. Use suitable refresh or short-lived policies and verify that restricted users cannot read private content through old links.
Test a matrix of roles
Test guest, member and administrator roles across sign-in, visibility, uploads, search and notifications. Track false positives alongside origin load and resolve narrowly scoped issues without disabling every control.