Protecting content can lead to unexpected results when combined with static caching. For example, you can password protect a page but as soon as you edit it, it becomes public. This is because the page is cached as soon as the authenticated user views it, making it public to non-authenticated users.
The simplest solution is to just exclude protected entries, and similar content, from the static cache, but I wonder if the middleware could be adjusted so that static caching can still be used safely on protected pages.
duncanmcclean
commented
3 months ago
Following on from this conversation.
Protecting content can lead to unexpected results when combined with static caching. For example, you can password protect a page but as soon as you edit it, it becomes public. This is because the page is cached as soon as the authenticated user views it, making it public to non-authenticated users.
The simplest solution is to just exclude protected entries, and similar content, from the static cache, but I wonder if the middleware could be adjusted so that static caching can still be used safely on protected pages.
Thanks.