The reader extension disables caching for content pages when permitted_groups is not empty.
Once a user with a permitted group access the page the response is cached, until then the correct action of redirecting for login takes place. (Not sure what happens if a user is logged in but doesn't have permission to view the page - possibly caches the permission_denied message?)
Could be a radiant core issue rather than reader, although in this case a workaround may be required to provide the reader functionality in the meantime?
The reader extension disables caching for content pages when permitted_groups is not empty.
Once a user with a permitted group access the page the response is cached, until then the correct action of redirecting for login takes place. (Not sure what happens if a user is logged in but doesn't have permission to view the page - possibly caches the permission_denied message?)
Could be a radiant core issue rather than reader, although in this case a workaround may be required to provide the reader functionality in the meantime?