You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some situations (where the "why" is definitely opinionated) people have multiple domains that access the same content e.g
mycooldomain.com - MAIN SITE
mycooldomain.net - MASK FOR MAIN SITE
mycooldomain.org - MASK FOR MAIN SITE
This module currently only supports the domain name it has been accessed from, that means if you access the administration panel via mycooldomain.com then only cache for the .com variant will be dynamically purged by this module.
Whilst you would think that in this situation, if you were to only purge the .com then the .net and .org will also reflect the purge as these domains only mask the original. Sadly that's not how CloudFlare works as it strictly caches the URL as a whole.
This issue is a poll to see if it would even be worth adding support for the above scenario where this module would also purge cache for all of your URL variants.
Please up vote one of the below comments
The text was updated successfully, but these errors were encountered:
Given the above references, I believe there may be a thirdparty, multi-domain extension in the pipeline for this module which would be exceptional in the fact that it doesn't have to be implemented within the base code itself
In some situations (where the "why" is definitely opinionated) people have multiple domains that access the same content e.g
This module currently only supports the domain name it has been accessed from, that means if you access the administration panel via
mycooldomain.com
then only cache for the.com
variant will be dynamically purged by this module.Whilst you would think that in this situation, if you were to only purge the .com then the .net and .org will also reflect the purge as these domains only mask the original. Sadly that's not how CloudFlare works as it strictly caches the URL as a whole.
This issue is a poll to see if it would even be worth adding support for the above scenario where this module would also purge cache for all of your URL variants.
Please up vote one of the below comments
The text was updated successfully, but these errors were encountered: