If content editors are changing/creating content on a subdomain such as admin.* the expire module is triggering a purge request using the FQD of http://admin.example.com/node/1234 format.

Because this isn't being cached at the edge the purge achieves nothing.

What i'd propose is a text field to define what the edge c-name is, and then amend the purge urls to use this c-name value. By default it would just be the $base_url value.

Happy to develop and submit a patch for this but wanted to check if there's any other edge cases to consider for this implementation?

Comments

stewsnooze’s picture

stewsnooze
he / him
commented

I've had to hack expire module before to support this. I'd like for this to be added.

budda’s picture

budda
Primary language English
Location Cheshire
commented

Probably best to implement this as an expire sub-module and provide a setting form alter and implement a hook to do the magic

function hook_expire_cache_alter(&$expire, &$node = NULL, &$paths) {
  // Add entries to $expire based on knowledge of the specific site.
}
budda’s picture

budda
Primary language English
Location Cheshire
commented
Status: Active » Fixed

Implemented as an add on module http://drupal.org/project/expire_alias

Status: Fixed » Closed (fixed)

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