Deprecated. This material represents early efforts and may be of interest to historians. It doe not describe current VIVO efforts.
Deprecated. This material represents early efforts and may be of interest to historians. It doe not describe current VIVO efforts.
VIVO adds headers to some HTTP responses, to assist in caching profile pages. Since release 1.6.
Overview
VIVO doesn't cache, but it helps to support caching.
How to enable cache awareness
What runtime properties are used to control it? Can it be controlled in developer mode?
What pages can be cached?
Only works on profile pages, and only if you are not logged in.
What do the caching headers look like?
Show a simple request with a cacheable response. Show a conditional request with a current ETag, Show a conditional request with a stale ETag.
How to configure your cache
It's up to you to insure that you don't cache something without an ETag. You should assume that all pages are stale.
Overview
Content Tools