HTTP cache
Component type
Categories
Maintenance status
Development status
Component created
Component changed
Proof-of-concept module providing HTTP caching for authenticated users.
How it works
By default any response - currently only pages rendered through drupal_render_page() - may be cached locally by the user agent, except if explicitly set not to (e.g. certain paths, or if the page contains dynamic content that changes every request). Along each cacheable response an ETag HTTP header is passed containing identifiers of all displayed data (entities, etc).
