Modify cache headers via configuration
Default Silverstripe cache handling sends headers that are not considered cacheable by a proxy such as Cloudflare.
This module allows you to modify this behaviour via configuration, allowing a proxy to cache based on the headers sent by the application.
This module is in development and is not yet suitable for production environments
Install via composer:
composer require nswdpc/silverstripe-cache-headers
The priority of caching directives in Silverstripe are in this order as follows:
disableCache($force=true) privateCache($force=true) publicCache($force=true) enableCache($force=true) disableCache() privateCache() publicCache() enableCache()
By default this module enables the cache (enableCache), but does not provide the force parameter as
See documentation for a primer on various options, including sample configurations.
We welcome bug reports, pull requests and feature requests on the Github Issue tracker for this project.
Please review the code of conduct prior to opening a new issue.
If you would like to make contributions to the module please ensure you raise a pull request and discuss with the module maintainers.
Please review the code of conduct prior to completing a pull request.
Module rating system helping users find modules that are well supported. For more on how the rating system works visit Module standards
Score not correct? Let us know there is a problem