You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The changes in #24 have disabled caching of all static files for authenticated users.
While it is good that Drupal private files (/system/files/*) should not be cached for authenticated users, there are lots of other static files that should still be safe candidates to cache. e.g. public files, css, js, images included in theme or module folders etc.
The text was updated successfully, but these errors were encountered:
I believe there's no need to cache such files in varnish. If you use nginx you can configure it to keep a "open files cache", which is as performant as Varnish in delivering static files.
The changes in #24 have disabled caching of all static files for authenticated users.
While it is good that Drupal private files (/system/files/*) should not be cached for authenticated users, there are lots of other static files that should still be safe candidates to cache. e.g. public files, css, js, images included in theme or module folders etc.
The text was updated successfully, but these errors were encountered: