Note: The code below uses new in the constructor which requires PHP 8. Start out with the external facing URL path and if needed do the internal URL path in a follow-up (the IS author assumes the external URLs are what gets cached). End consumers of URLs created this way can then add the cacheability information as needed. StreamWrappers can start emitting this modified string and the layers consuming StreamWrappers must be adjusted to preserve this information or promote a string to a CacheableString if this has not been done.
Introduce a CacheableString class in Drupal which can be used to associate cacheability information with strings, by implementing the PHP 8.0 Stringable interface this class is mostly backward compatible with normal strings*. However Drupal does not currently allow providing cacheability information from a StreamWrapper which means that a link with an expiration date could get stuck in a page cache and be served to future users leading to a broken page.įlysystem could be another benefactor of this with the underlying library supporting "Temporary URLs" for many cloud providers, but the Drupal module not currently being able to support those types of URLs. This provides a good combination of public and private file system where a leaked link will stop working at some point but all requests in the meantime can be served by a CDN. StreamWrappers provide a good way to build a hybrid system where the access of the field containing the image proofs access, allowing the generation of a static but expiring link. This can be seen in community platforms like built with Open Social where a majority of the traffic is authenticated but will still see similar pages. The private file system uses static links for the files which requires Drupal to check access for every request, making the files uncacheable.įor sites that have a large amount of users and served files that require protection, the public file system is undesirable because any leaked link never expires, but the private file system is also undesirable because it can put a huge strain on Drupal. The public file system has as advantage that links can be served by a webserver rather than Drupal but this offers no protection. Drupal 8 also has some clever ideas, with using placeholders in caches, so it can cache rendered html of a page with placeholder for username and simply swap username based on logged in user. Hybrid systems with expirable URLs are useful in many circumstances but create conflicts with Drupal's page caches because a URL currently can't have cacheability metadata.īy default Drupal forces installations to choose between a public file system or a private file system. The clever thing behind Drupal's caching, is that it merges items, to parts the are general could use a common cache. TL DR: The lack of cacheability metadata in StreamWrappers make it impossible to create links to files that are not either "static unsafe URLs without access-time check" or "static URLs with mandatory access-time check". Drupal 10.1 Cache.php class Cache Same name and namespace in other branches Helper methods for cache.
0 kommentar(er)
