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.
I am using Varnish 3.0.2, expire 7.x-2.0-rc2 and varnish 7.x-1.0-beta2 to purge Varnish selectively.
While scanning the list of bans in varnish, I saw req.url ~ ^<front>$
which is clearly a problem, as the correct ban request would point to req.url ~ ^/$
.
Below is a trivial patch that I applied to my exipre module to fix the issue.
Comment | File | Size | Author |
---|---|---|---|
#1 | frontpage-not-cleaned-by-varnish-2232283-1.patch | 1.84 KB | mikhailian |
Comments
Comment #1
mikhailian CreditAttribution: mikhailian commentedComment #2
quotesBro CreditAttribution: quotesBro commentedI guess this issue is related to #2206761: Frontpage not expired
Comment #3
SpleshkaFixed in related issue #2206761: Frontpage not expired
Comment #4
Island Usurper CreditAttribution: Island Usurper commentedWhile #2206761: Frontpage not expired works in most cases, calling
drush xp-path FRONT
still sends<front>
to Varnish. drush_expire_internal_path() needs to take ExpireAPI::getFrontPageUrls() into account.Comment #6
SpleshkaThanks for this hint, I hope that now this issue has been fixed.
Comment #8
Liam Morland