Hi all

Someone has used 'meta cache-control' tag  individually on the pages, in order to change the configuration authenticated cache in Host? I'm thinking of leaving the host as 'PUBLIC', and most sensitive pages use the 'meta cache-control = "ServerNoCache"' default.

What do you think?

Hugs

---

Comunidade BrasilDNN Marcio Maciel, Brasil

Hi Cathal

I'm looking for performance, and understand the privacy and security risks involved in caching on the user's browser. But I think this should be configured the page level.

As in the portal and in the pages there is no specific options to configure this, so I thought the opposite: use host configuration "Authenticated Cacheability = PUBLIC", what would that all pages in all portals would be using the best performance possible, but in one or another page that need to protect data would use the setting 'Page Header Tags: meta cache-control=ServerAndNoCache'.

What do you think?

About go behind a module or something, I do not see the need for this kind of thing, maybe include how New Features in Gemini?

Hugs

---

Comunidade BrasilDNN Marcio Maciel, Brasil

Hi Sebastian and Cathal

I logged feature in Gemini. Now, another question: If I understand correctly, the host configuration affects only authenticated users. But what the meta cache-control used by DNN to pages accessed by anonymous users?

Hugs

---

Comunidade BrasilDNN Marcio Maciel, Brasil