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.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mikhailian’s picture

Title: Fronpage is not clean in Varnish because it is reported as <front> and not as / » Fronpage is not cleaned in Varnish because it is reported as <front> and not as / by expire
FileSize
1.84 KB
quotesBro’s picture

Version: 7.x-2.0-rc2 » 7.x-2.x-dev
Status: Active » Needs review

I guess this issue is related to #2206761: Frontpage not expired

Spleshka’s picture

Status: Needs review » Closed (duplicate)

Fixed in related issue #2206761: Frontpage not expired

Island Usurper’s picture

Title: Fronpage is not cleaned in Varnish because it is reported as <front> and not as / by expire » Fronpage is not cleaned in Varnish by Drush because it is reported as <front> and not as / by expire
Status: Closed (duplicate) » Active

While #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.

  • Spleshka committed 84cec7e on 7.x-2.x
    Issue #2232283 by Spleshka, Island Usurper, mikhailian: Frontpage is not...
Spleshka’s picture

Status: Active » Fixed

Thanks for this hint, I hope that now this issue has been fixed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

Liam Morland’s picture

Title: Fronpage is not cleaned in Varnish by Drush because it is reported as <front> and not as / by expire » Frontpage is not cleaned in Varnish by Drush because it is reported as <front> and not as / by expire