i'm running issues caching on drupal 7 site, seems users receiving stale pages, despite not having "cache pages" or "cache blocks" settings enabled. there no additional server-side caching enabled, , we're not using cdn. i've cleared cache via drush cc all, clearing cache through ui.
after clearing cache, , js aggregation enabled, i've pulled pages receive old version of js. aggregation turned off, new js, expected. turn aggregation on , pull page in incognito window, , old js.
however, aggregation turned off, i've seen in our logs we're getting "page not found" messages expired, aggregated js & css files. indicates me users getting served pages references these old files, though i'm open other possibilities.
the headers our homepage include cache-control: no-cache, must-revalidate , expires value in past. headers our main.js file include cache-control: max-age=1209600, etag value, , expires value set 2 weeks now. clearing drupal caches, there should update etag value on changed files force users download updated asset, correct? in case of stale pages & aggregated files, users don't seem requesting updated aggregated file. our hosting support has suggested settings on these assets may impacting upstream cache (i'm assuming mean cache on homepage, example).
in short, i'm seeing requests assets linked stale page, seems there page caching that's happening on level. since don't have server-side caching or page / block caching set through drupal, possible cache settings on assets impacting page cache? why else might see requests expired assets?
i have question on drupal.stackexchange.com well, seems possible related broader caching issue.
Comments
Post a Comment