Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Grade F on Add Expires headers
There are 19 static components without a far-future expiration date.
Most of the elements are from the advagg_js and advagg_css directories
Comment | File | Size | Author |
---|---|---|---|
#8 | advagg-2088563-8-detect-loopback-issues.patch | 2.79 KB | mikeytown2 |
#5 | advagg-2088563-5-test-cdn-path.patch | 19.13 KB | mikeytown2 |
#3 | Screen Shot 2013-09-15 at 10.33.41.png | 178.81 KB | BarisW |
Comments
Comment #1
mikeytown2 CreditAttribution: mikeytown2 commentedIf you go to the status report page
admin/reports/status
what does that report for AdvAgg?Comment #2
mikeytown2 CreditAttribution: mikeytown2 commentedComment #3
BarisW CreditAttribution: BarisW commentedI have this same issue. All lights on the reports page are green, but pagespeedtest report missing expires headers. See screenshot.
Without Advagg enabled, this does not happen.
Comment #4
OriginalSauce CreditAttribution: OriginalSauce commentedHi,
Although I did not get the same message from webpagetest, I did have a similar issue that stopped the far future headers being set. (and the report status page was all green)
I found a conflicting server configuration that was causing the directives set in the .htaccess file, found in advagg file paths, to be ignored.
It's probably not what you are experiencing, but it is worth checking that the .htaccess directives are being applied.
Comment #5
mikeytown2 CreditAttribution: mikeytown2 commentedI've committed this change; it will change the blacklists to be blank before file_create_url is ran. Default auth blacklist is admin*; this change will now test the normal and CDN path on the status page.
Diff isn't clear but I added in this bit of logic
Comment #6
BarisW CreditAttribution: BarisW commentedActually, it seemed that I needed to enable the mod_rewrite. That solved the issue.
What's weird is that all lights were green in the Status Reports page.
I've tried DEV and the issue is still there.
Comment #7
mikeytown2 CreditAttribution: mikeytown2 commentedMy only guess as to why the headers come back ok on the status page is that the internal HTTP request is hitting drupal, where as external HTTP requests are hitting apache and bypassing Drupal. I should be able to detect if this is happening but I can't think of a way to code around this unless using some sort of open proxy (like http://en.wikipedia.org/wiki/Coral_Content_Distribution_Network add .nyud.net to the end of the hostname and try again if website is externally routable).
Comment #8
mikeytown2 CreditAttribution: mikeytown2 commentedI've added in a check to see if the file was generated on demand (from drupal) or served via Apache. I'll be adding in documentation on what to do in this issue #2097033: "cache-control's max-age header" and "The expires header"
Comment #9
BarisW CreditAttribution: BarisW commentedAmazing, thanks!