If this module is used on a Domain Access-enabled site, or on a site with multiple domains configured in some other way, there's a good possibility that one path might be accessible through multiple domains.
Currently, only the domain that's actively being used when, for example, hook_node_update() is hit is cleared.
So if you have:
And the content editor is logged in at www.example.com, only www.example.com/path would be cleared.
Modules like Acquia Purge have configuration variables like acquia_purge_domains to allow for multiple domains to be configured explicitly, and supporting this kind of functionality doesn't seem like it would be too difficult to do, likely only involving a few changes in AkamaiCacheControlClient to make basepath able to be an array of base paths.
| Comment | File | Size | Author |
|---|
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #1
geerlingguy commentedTaking an initial stab at this; the patch adds a new
akamai_additional_basepathsvariable that can store additional domains, but doesn't expose this advanced parameter to the admin UI, mostly because it should be pretty rare that a site needs to use it.Comment #2
diamondseaHave you tried the Expire Alias module: https://www.drupal.org/project/expire_alias
It sounds like it might do what you're looking for.
Comment #3
damienmckennaThe 7.x-3.x codebase changed a good bit and it now uses the "akamai_hostname" variable instead of "akamai_basepath". And a note should be added to the README file explaining its usage.
Comment #4
damienmckennaThis patch expands usage of the current "akamai_hostname" variable so that it allows multiple hostnames to be provided, just by separating them with a space.
Comment #5
WidgetsBurritos commentedPostponed pending #3244672: Seeking 7.x Maintainer
Comment #6
moshe weitzman commentedThis is needed on the current branch as well, so reopening. If this is already possible there, feel free to close. Thanks.
Comment #7
moshe weitzman commentedComment #10
ajitsCreated a merge request that adds a new setting to add multiple base paths. The older basepath is still deprecated and preserved for backwards compatibility. An upgrade path is also provided.
Comment #11
ajitsCreated #3546437: Allow purging sub-domains of basepath that should solve sub-domain issue. This issue could track multiple domains.
Comment #12
plachComment #13
ajitsFeedback addressed.
Also closed #3546437: Allow purging sub-domains of basepath in favor of this issue.
Comment #14
plachLooks good and works well, thanks!
Comment #15
plachActually, this is introducing some CI warnings.
Comment #16
ajitsThe failure is in "Composer (next major)" build step. I tried to run a new pipeline. The normal "Composer" build passes. There are other PRs that fail at the composer step too. This doesn't seem to be related to the fixes made.
Comment #20
smustgrave commentedThis one appears to have been reviewed and fine tuned already. Going to include in 6.0.x for sure.
Since the MR on 5.0x was done went ahead and included there too.