Experimental project
This is a sandbox project, which contains experimental code for developer use only.
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).
Subsequent requests will now pass a If-None-Match request-header field. During bootstrap all identifiers in the ETag will be checked for freshness. If all identifiers are fresh, a 304 Not Modified response will be returned.
Project information
- Minimally maintained
Maintainers monitor issues, but fast responses are not guaranteed. - Module categories: Performance
- Created by casey on , updated