PageCache

enum PageCache

How browsers and caches may keep the responses routes serves for pages.

It applies to rendered pages, error pages, redirects, and HTTP route responses that set no Cache-Control of their own. Scalive's browser files keep their own headers. A page carries its CSRF token and signed session, so no case lets a shared cache keep it.

Defined by scalive.PageCache. View source (scalive/transport/zio-http/src/scalive/PageCache.scala:12-30)

Values2

val NoStore: PageCache

no-store: nothing keeps the page, for applications whose pages hold sensitive data.

Defined by scalive.PageCache.NoStore. View source (scalive/transport/zio-http/src/scalive/PageCache.scala:19-19)

val Revalidate: PageCache

private, max-age=0, must-revalidate, as Phoenix sends by default: only the browser may keep the page, and it asks the server again before reusing it.

Defined by scalive.PageCache.Revalidate. View source (scalive/transport/zio-http/src/scalive/PageCache.scala:16-16)